Electronic device for sharing data and method for controlling the same

ABSTRACT

A method for sharing data in a transmitting-side electronic device communicating with a receiving-side electronic device is provided. The method includes connecting a voice call with the receiving-side electronic device; obtaining a sharing object to be shared with the receiving-side electronic device; and transmitting data corresponding to the sharing object to the receiving-side electronic device through a data session formed based on information related to the voice call.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation of U.S. application Ser. No. 14/600,872 filed onJan. 20, 2015, which claims priority under 35 U.S.C. § 119(a) of U.S.Patent Application No. 61/929,234 filed in the United States Patent andTrademark Office on Jan. 20, 2014, U.S. Patent Application No.61/936,713 filed in the United States Patent and Trademark Office onFeb. 6, 2014, Korean Patent Application No. 10-2014-0020906 filed in theKorean Intellectual Property Office on Feb. 21, 2014, Korean PatentApplication No. 10-2014-0020888 filed in the Korean IntellectualProperty Office on Feb. 21, 2014, and Korean Patent Application No.10-2014-0125168 filed in the Korean Intellectual Property Office on Sep.19, 2014, the entire disclosures of all of which are incorporated hereinby reference in their entireties.

TECHNICAL FIELD

Methods and apparatuses consistent with the exemplary embodiments relateto an electronic device and a control method of the electronic device,and more particularly, to an electronic device and a control method forefficiently sharing data.

BACKGROUND

Technological advances related to electronic devices, and controlmethods thereof, have developed rapidly. In particular, the electronicdevices may provide voice call functions. In other words, the voice callfunction may be provided between a transmitting-side electronic deviceand a receiving-side electronic device.

The electronic device may not provide additional functions incombination with the voice call.

Specifically, to perform additional tasks during the voice call, theelectronic device would have to run a separate application. This wouldbe very inconvenient to users.

SUMMARY

An aspect of the exemplary embodiments addresses at least theabove-mentioned problems and/or disadvantages and provides at least theadvantages described below. Accordingly, an aspect of an exemplaryembodiment of the present disclosure provides an electronic device forsharing data corresponding to a sharing object with a receiving-sideelectronic device during a voice call connection, and a method forcontrolling the same.

In accordance with an aspect of the exemplary embodiments, there isprovided a method for sharing data in a transmitting-side electronicdevice communicating with a receiving-side electronic device. The methodincludes connecting a voice call with the receiving-side electronicdevice; obtaining a sharing object to be shared with the receiving-sideelectronic device; and transmitting data corresponding to the sharingobject to the receiving-side electronic device through a data sessionformed based on information related to the voice call.

In accordance with another aspect of the exemplary embodiments, there isprovided a method for sharing data in a receiving-side electronic devicecommunicating with a transmitting-side electronic device. The methodincludes connecting a voice call with the transmitting-side electronicdevice; and receiving data corresponding to a sharing object to beshared with the transmitting-side electronic device from thetransmitting-side electronic device through a data session formed basedon information related to the voice call.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses exemplary embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of certainexemplary embodiments of the present disclosure will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates a network environment including an electronic deviceaccording to various exemplary embodiments;

FIG. 2 is a schematic block diagram of a data sharing module included ina data sharing electronic device according to an exemplary embodiment;

FIG. 3 illustrates data sharing electronic devices being connected to amobile network according to an exemplary embodiment;

FIGS. 4 and 5 are flowcharts for a control method of data sharingelectronic devices according to an exemplary embodiment;

FIGS. 6A-6E, 7A, 7B, 8A-8C, 9A-9C, 10A, 10B, 11A, 11B, 12A, and 12Billustrate execution screens of data sharing electronic devicesaccording to an exemplary embodiment;

FIG. 13 is a flowchart for a control method of data sharing electronicdevices according to another exemplary embodiment;

FIGS. 14A-14C and 15A-15C illustrate execution screens of data sharingelectronic devices according to another exemplary embodiment;

FIG. 16 is a flowchart for a control method of data sharing electronicdevices according to another exemplary embodiment;

FIGS. 17A, 17B, 18A, 18B, 19A, 19B, 20A, 20B, 21A-21C, and 22 illustrateexecution screens of data sharing electronic devices according toanother exemplary embodiment;

FIG. 23 is a block diagram of an electronic device according to variousexemplary embodiments;

FIG. 24 illustrates a communication protocol between a plurality ofelectronic devices according to various exemplary embodiments;

FIG. 25 illustrates devices that are connected in a control method ofelectronic devices having a function of sharing content in voicecommunication according to an exemplary embodiment;

FIGS. 26A and 26B are flowcharts for a control method of an electronicdevice having a function of sharing content in voice communicationaccording to various exemplary embodiments;

FIGS. 27A, 27B, 28A-28C, 29A, 29B, 30A, and 30B illustrate executionscreens of an electronic device having a function of sharing content invoice communication according to an exemplary embodiment;

FIG. 31 is a flowchart for a control method of electronic devices havinga function of sharing content in voice communication according toanother exemplary embodiment;

FIGS. 32A-32C, 33A, 33B, 34, 35A, and 35B illustrate execution screensof electronic devices having a function of sharing content in voicecommunication according to another exemplary embodiment;

FIG. 36 is a flowchart for a control method of an electronic devicehaving a function of sharing content in voice communication according tofurther another exemplary embodiment;

FIGS. 37A-37C, 38A-38C, 39A, 39B, 40A-40C, 41A-41C, 42A, and 42Billustrate execution screens of an electronic device having a functionof sharing content in voice communication according to further anotherexemplary embodiment;

FIGS. 43A and 43B are flowcharts for a control method of electronicdevices having a function of sharing content in voice communicationaccording to another exemplary embodiment;

FIGS. 44A, 44B, 45A, 45B, 46A-46C, 47A-47C, 48A, and 48B illustrateexecution screens of electronic devices having a function of sharingcontent in voice communication according to another exemplaryembodiment;

FIG. 49 is a flowchart of a data sharing method according to variousexemplary embodiments;

FIG. 50 is a flowchart of a data sharing method according to variousexemplary embodiments;

FIGS. 51A, 51B, 52A, 52B, 53A, 53B, 54A, 54B, 55A, 55B, 56A, 56B, 57A,57B, 58A, 58B, 59A, 59B and 60 illustrate screens displayed by atransmitting-side electronic device and a receiving-side electronicdevice according to various exemplary embodiments;

FIG. 61 is a flowchart for a data sharing method of a transmitting-sideelectronic device according to various exemplary embodiments;

FIG. 62 is a flowchart for a data sharing method of a receiving-sideelectronic device according to various exemplary embodiments o;

FIG. 63 is a flowchart of a data sharing method according to variousexemplary embodiments;

FIGS. 64A and 64B illustrate screens displayed by an electronic deviceaccording to various exemplary embodiments;

FIG. 64C is a flowchart of a data sharing method according to anexemplary embodiment;

FIGS. 65A and 65B illustrate screens displayed by an electronic deviceaccording to various exemplary embodiments;

FIG. 66 is a conceptual diagram illustrating a system hierarchyaccording to various exemplary embodiments;

FIGS. 67A to 67D are flowcharts of a data sharing method according tovarious exemplary embodiments; and

FIG. 68 is a block diagram of a heterogeneous application processingagent in view of modules according to various exemplary embodiments.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the exemplary embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of exemplary embodiments of thepresent disclosure is provided for illustration purpose only and not forthe purpose of limiting the disclosure as defined by the appended claimsand their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

By the term “substantially” it is meant that the recited characteristic,parameter, or value need not be achieved exactly, but that deviations orvariations, including for example, tolerances, measurement error,measurement accuracy limitations and other factors known to those ofskill in the art, may occur in amounts that do not preclude the effectthe characteristic was intended to provide.

An electronic device according to various exemplary embodiments of thepresent disclosure may be a device equipped with a communicationfunction. For example, the electronic device may include at least one ofa smart phone, a tablet Personal Computer (PC), a mobile phone, a videophone, an e-book reader, a desktop PC, a laptop PC, a netbook computer,a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP),an MP3 player, a mobile medical device, a camera, and a wearable device(e.g., a Head Mounted Device (HMD) (such as electronic eyeglasses),electronic apparel, electronic bracelet, electronic necklace, electronicappcessory, electronic tattoo, or smart watch). However, the electronicdevice is not limited thereto.

In certain exemplary embodiments, the electronic device may be a smarthome appliance equipped with a communication function. The smart homeappliance may include at least one of, for example, a Television (TV), aDigital Video Disk (DVD) player, an audio player, a refrigerator, an airconditioner, a vacuum cleaner, an oven, a microwave oven, a washer, anair purifier, a set-top box, a TV box (e.g., Samsung HomeSync™, an AppleTV™, or a Google TV™), a game console, an electronic dictionary, anelectronic key, a camcorder and an electronic photo frame.

In certain exemplary embodiments, the electronic device may include atleast one of various medical devices (e.g., Magnetic ResonanceAngiography (MRA), Magnetic Resonance Imaging (MRI), Computed Tomography(CT), a medical camcorder, a medical ultrasonic device, or the like), anavigation device, a Global Positioning System (GPS) receiver, an EventData Recorder (EDR), a Flight Data Recorder (FDR), an automotiveinfotainment device, a marine electronic device (e.g., a marinenavigation device, a gyro compass, or the like), a avionics, a securitydevice, a car head unit, an industrial or household robot, an AutomaticTeller's Machine (ATM) for banks, and a Point Of Sales (POS) for shops.

In certain exemplary embodiments, the electronic device may include atleast one of a part of the furniture or building/structure equipped witha communication function, an electronic board, an electronic signaturereceiving device, a projector, and various metering devices (e.g., awater meter, an electricity meter, a gas meter, a radio wave meter, orthe like). The electronic device according to various exemplaryembodiments of the present disclosure may be one of the above-describedvarious devices, or a combination thereof. In addition, the electronicdevice according to various exemplary embodiments of the presentdisclosure may be a flexible device. It will be apparent to those ofordinary skill in the art that the electronic device according tovarious exemplary embodiments of the present disclosure is not limitedto the above-described devices.

The electronic device according to various exemplary embodiments of thepresent disclosure will be described below with reference to theaccompanying drawings. The term ‘user’ as used herein may refer to aperson using the electronic device, or a device (e.g., an intelligentelectronic device) using the electronic device.

FIG. 1 illustrates a network environment 100 including an electronicdevice 101 according to various exemplary embodiments of the presentdisclosure. Referring to FIG. 1, the electronic device 101 may include abus 110, a processor 120, a memory 130, an Input/Output (I/O) interface140, a display 150, a communication interface 160, and a data sharingmodule 170.

The bus 110 may be a circuit that connects the above-describedcomponents to each other, and sends communication signals (e.g., controlmessages) between the components.

The processor 120 may, for example, receive a command from the othercomponents (e.g., the memory 130, the I/O interface 140, the display150, the communication interface 160, the data sharing module 170, orthe like) through the bus 110, decrypt the received command, and executean operation or data processing based on the decrypted command.

The memory 130 may store the command or data, which is received from theprocessor 120 or the other components (e.g., the I/O interface 140, thedisplay 150, the communication interface 160, the data sharing module170, or the like), or generated by the processor 120 or the othercomponents. The memory 130 may include programming modules such as, forexample, a kernel 131, a middleware 132, an Application ProgrammingInterface (API) 133, or an application(s) 134. Each of the programmingmodules may be configured by one of software, firmware and hardware, ora combination thereof.

The kernel 131 may control or manage the system resources (e.g., the bus110, the processor 120, the memory 130, or the like) used to execute theoperation or function implemented in the other programming modules(e.g., the middleware 132, the API 133 or the application 134). Thekernel 131 may provide an interface through which the middleware 132,the API 133 or the application 134 can access the individual componentsof the electronic device 101, and control or manage the components.

The middleware 132 may play an intermediary role so that the API 133 orthe application 134 may communicate with the kernel 131 to exchange datawith each other. With respect to the word requests received from theapplication 134, the middleware 132 may, for example, perform control(e.g., scheduling or load balancing) for a work request, using a methodsuch as assigning the priority for using the system resources (e.g., thebus 110, the processor 120, the memory 130, or the like) of theelectronic device 101, to at least one of the application(s) 134.

The API 133 may include, for example, at least one interface or function(e.g., command) for file control, window control image processing orcharacter control, as an interface through which the application 134controls the function provided from the kernel 131 or the middleware132.

In various exemplary embodiments, the application 134 may include aShort Message Service (SMS)/Multimedia Messaging Service (MMS)application, an e-mail application, a calendar application, an alarmapplication, a healthcare application (e.g., an application formeasuring the amount of exercise or the blood glucose), or anenvironmental information application (e.g., an application forproviding the pressure, humidity or temperature information).Additionally or alternatively, the application 134 may be an applicationrelated to information exchange between the electronic device 101 and anexternal electronic device (e.g., an electronic device 104). Theinformation exchange-related application may include, for example, anotification relay application for relaying specific information to theexternal electronic device, or a device management application formanaging the external electronic device.

For example, the notification relay application may include a functionof relaying the notification information generated in other applications(e.g., the SMS/MMS application, the e-mail application, the healthcareapplication, the environmental information application, or the like) ofthe electronic device 101, to the external electronic device (e.g., theelectronic device 104). Additionally or alternatively, the notificationrelay application may, for example, receive notification informationfrom the external electronic device (e.g., the electronic device 104)and provide the received notification information to the user. Thedevice management application may, for example, manage a function (e.g.,a function of turning on/off the external electronic device itself (orsome components thereof) or adjusting the brightness (or resolution) ofa display thereof) of at least a part of the external electronic device(e.g., the electronic device 104) communicating with the electronicdevice 101, or may manage (e.g., install, delete or update) theapplication operating in the external electronic device or the service(e.g., a call service or a message service) provided from the externalelectronic device 104.

In various exemplary embodiments, the application 134 may include anapplication that is specified according to the properties (e.g., thetype of an electronic device) of the external electronic device (e.g.,the electronic device 104). For example, if the external electronicdevice is an MP3 player, the application 134 may include an applicationrelated to music playback. Similarly, if the external electronic deviceis a mobile medical device, the application 134 may include anapplication related to healthcare. In one exemplary embodiment, theapplication 134 may include at least one of an application specified inthe electronic device 101, and an application received from the externalelectronic device (e.g., a server 106 or the electronic device 104).

The I/O interface 140 may, for example, send the command or data that isreceived from the user through an I/O device (e.g., a sensor, a keyboardor a touch screen), to the processor 120, the memory 130, thecommunication interface 160 or the data sharing module 170 through thebus 110. For example, the I/O interface 140 may provide the data for auser's touch input on the touch screen, to the processor 120. The I/Ointerface 140 may, for example, output the command or data that isreceived from the processor 120, the memory 130, the communicationinterface 160 or the data sharing module 170 through the bus 110, to theoutside through the I/O device (e.g., a speaker or a display). Forexample, the I/O interface 140 may output the voice data that isprocessed by the processor 120, to the user through the speaker.

The display 150 may display a variety of information (e.g., multimediadata, text data, or the like) for the user, and may be formed as a touchscreen to provide a user input interface by use of a pen or the fingersof a user.

The communication interface 160 may communicatively connect theelectronic device 101 and the external electronic devices (e.g., theelectronic device 104 or the server 106). For example, the communicationinterface 160 may be connected to a network 162 through wired/wirelesscommunication, to communicate with the external electronic device. Thewireless communication may include at least one of, for example,Wireless Fidelity (WiFi), Bluetooth (BT), Near Field Communication(NFC), GPS, and cellular communication (e.g., Long Term Evolution (LTE),LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), WidebandCDMA (WCDMA), Universal Mobile Telecommunications System (UMTS),Wireless Broadband (WiBro), Global System for Mobile communications(GSM), or the like). The wired communication may include at least oneof, for example, Universal Serial Bus (USB), High Definition MultimediaInterface (HDMI), Recommended Standard 232 (RS-232), and Plain OldTelephone Service (POTS).

In one exemplary embodiment, the network 162 may be a telecommunicationsnetwork. The telecommunications network may include at least one of acomputer network, the Internet, Internet of Things (IoT), and atelephone network. In one exemplary embodiment, a protocol (e.g., atransport layer protocol, a data link layer protocol or a physical layerprotocol) for communication between the electronic device 101 and theexternal electronic device 104 may be supported by at least one of theapplication 134, the API 133, the middleware 132, the kernel 131 or thecommunication interface 160.

FIG. 2 is a schematic block diagram of a data sharing module included ina data sharing electronic device according to an exemplary embodiment ofthe present disclosure.

Referring to FIG. 2, the data sharing module 170 may include a voicecall module 210, a sharing object display module 220, a sharing requestand reception module 230, a real-time data sharing module 240, and acontrol command execution module 250.

The data sharing module 170 may be incorporated into the processor 120.The processor 120 may collectively control the data sharing module 170.

The voice call module 210 may connect a voice call, with areceiving-side electronic device. The sharing object display module 220may display a sharing object on a display. The sharing request andreception module 230 may detect a selection of the sharing object, andif the sharing object is selected, the sharing request and receptionmodule 230 may request sharing of data corresponding to the sharingobject from the receiving-side electronic device, and receive a sharingacceptance for the data from the receiving-side electronic device. Thereal-time data sharing module 240 transmits the requested data to thereceiving-side electronic device in real time to share the requesteddata in real time. The control command execution module 250 may executethe control command related to the shared data in the same way as thereceiving-side electronic device. Although the shared data may include,for example, music, photos, video, texts, web content and elements, theshared data is not limited thereto in the exemplary embodiments of thepresent disclosure.

FIG. 3 illustrates data sharing electronic devices connected to a mobilenetwork according to an exemplary embodiment of the present disclosure.Referring to FIG. 3, a transmitting-side electronic device 101, areceiving-side electronic device 104, a relay server 300, and a callserver 310 may be connected to a mobile network to perform communicationwith each other.

FIGS. 4 and 5 are flowcharts for a control method of data sharingbetween electronic devices according to an exemplary embodiment of thepresent disclosure. FIGS. 6 to 12 illustrate execution screens of datasharing electronic devices according to an exemplary embodiment of thepresent disclosure.

Referring to FIGS. 4 and 5, a transmitting-side electronic device 101and a receiving-side electronic device 104 may subscribe to a sharingservice in a relay server 300 in operations 400 and 402. A processor 120of the transmitting-side electronic device 101 may send a subscriptionrequest for the sharing service to the relay server 300. In response tothe subscription request for the sharing service from thetransmitting-side electronic device 101, the relay server 300 may send asubscription acceptance response message for the sharing service to thetransmitting-side electronic device 101 in operation 400. In addition,the receiving-side electronic device 104 may also send a subscriptionrequest message for the sharing service to the relay server 300 in thesame way as the transmitting-side electronic device 101 in operation402.

The processor 120 of the transmitting-side electronic device 101 maysend an identifier for identifying the transmitting-side electronicdevice 101 to the relay server 300. Therefore, the relay server 300 mayidentify the transmitting-side electronic device 101 based on thereceived identifier. A processor of the receiving-side electronic device104 may also store an identifier for identifying the receiving-sideelectronic device 104 in the relay server 300. Therefore, the relayserver 300 may identify the receiving-side electronic device 104 basedon the received identifier. In addition, the relay server 300 mayreceive the pre-registered counterpart SNS information and profileinformation (images, alias and the like), which can be provided on ascreen (or a voice call dialing screen) of a phone application or ascreen of a contact application (or a contact list phonebook), from thecounterpart electronic device, and provide the received information.

Next, the transmitting-side electronic device 101 may connect a voicecall with the receiving-side electronic device 104 in operation 410. Thetransmitting-side electronic device 101 may connect a voice call withthe receiving-side electronic device 104 over a mobile network. In thiscase, the transmitting-side electronic device 101 may connect a voicecall with the receiving-side electronic device 104 through a call server310. For example, the processor 120 of the transmitting-side electronicdevice 101 may send a request for connecting a voice call with thereceiving-side electronic device 104, to the call server 310. Inresponse to the connection request, the call server 310 may send anacceptance request for the voice call connection to the receiving-sideelectronic device 104. In response to the acceptance request, the callserver 310 may connect the voice call between the transmitting-sideelectronic device 101 and the receiving-side electronic device 104.

For example, the transmitting-side electronic device 101 may run a phoneapplication and send a request for a voice call connection with thereceiving-side electronic device 104 to the call server 310. Referringto FIGS. 6A to 6E, as shown in FIG. 6A, the processor 120 of thetransmitting-side electronic device 101 may run a phone application 600and display the phone application 600 on the display 150. As shown inFIG. 6B, the processor 120 of the transmitting-side electronic device101 may run a contact application which stores a list of contacts of auser of the transmitting-side electronic device, and receive an inputfor a selection of a contact corresponding to a user of thereceiving-side electronic device 104. In addition, the processor 120 ofthe transmitting-side electronic device 101 may receive a callconnection command. For example, in FIG. 6B, the processor 120 of thetransmitting-side electronic device 101 may receive an input for aselection of a contact corresponding to the receiving-side electronicdevice 104, such as ‘Kimberly Lopez’ 612. As shown in FIG. 6C, theprocessor 120 of the transmitting-side electronic device 101 may send arequest for a voice call connection with the receiving-side electronicdevice 104 corresponding to ‘Kimberly Lopez’ 612, to the call server310. In this case, as shown in FIG. 6C, the processor 120 of thetransmitting-side electronic device 101 may display a Call Connecting(or Alerting) image 622 on the display 150. In response to theconnection request, the call server 310 may send an acceptance requestfor the voice call connection to the receiving-side electronic device104. As shown in FIG. 6D, the processor of the receiving-side electronicdevice 104 may display a Call Receiving (or Ringing) image 641 on itsdisplay. The receiving-side electronic device 104 may send itsacceptance for the voice call connection to the call server 310. Inresponse to the acceptance request, the call server 310 may connect thevoice call between the transmitting-side electronic device 101 and thereceiving-side electronic device 104. As shown in FIG. 6E, the processor120 of the transmitting-side electronic device 101 may display a PhoneConversation image 631 on the display 150.

Next, in operation 412, the transmitting-side electronic device 101 maydisplay a sharing object on the display 150. In other words, theprocessor 120 of the transmitting-side electronic device 101 may displaya sharing object on the display 150. For example, the sharing object maybe an icon symbolizing the type of the data corresponding to the sharingobject. In addition, the data may be, for example, audio streaming, anInternet Uniform Resource Locator (URL), an image, an event orcoordinates.

For example, as shown in FIG. 6E, the processor 120 may display sharingobjects 634 to 638 on the display 150. The sharing objects may be formedas one or more icons 634 to 638 in a bar-shaped area 632. The sharingobjects may be displayed on a Phone Conversation screen 630. The sharingobjects may be transparently formed on the Phone Conversation image 631displayed on the Phone Conversation screen 630. Alternatively, thesharing objects may be displayed at the bottom of the Phone Conversationimage 631.

At least one of the icons may symbolize the type of the data. Forexample, among the icons shown in FIG. 6E, the Image icon 634 maysymbolize an image, such as email, in the data, the Internet icon 636may symbolize an Internet URL in the data, and the Audio icon 638 maysymbolize audio streaming in the data.

As described below, if the Image icon 634 is selected, data concerningthe image may be shared between the transmitting-side electronic device101 and the receiving-side electronic device 104. If the Internet icon636 is selected, data concerning the Internet URL may be shared betweenthe transmitting-side electronic device 101 and the receiving-sideelectronic device 104. If the Audio icon 638 is selected, dataconcerning the audio streaming may be shared between thetransmitting-side electronic device 101 and the receiving-sideelectronic device 104.

Next, in operation 414, the transmitting-side electronic device 101 maydetect a selection of the sharing object. The processor 120 of thetransmitting-side electronic device 101 may detect a selection of thesharing object. For example, the processor 120 may detect a touch on theicon corresponding to the sharing object. If the touch on the icon isdetected, the processor 120 may detect a selection of the sharing objectcorresponding to the icon.

For example, in FIG. 6E, the processor 120 may detect a touch on theAudio icon 638. If a touch on the Audio icon 638 is detected, theprocessor 120 may detect a selection of the sharing object correspondingto the Audio icon 638.

Next, if the sharing object 634 is selected, the transmitting-sideelectronic device 101 may send a request for sharing of datacorresponding to the sharing object, to the receiving-side electronicdevice 104. In this case, the processor 120 of the transmitting-sideelectronic device 101 may send the request for sharing of data to thecall server 310 in operation 420. The call server 310 may send thesharing request to the receiving-side electronic device 104 in operation422.

If the sharing object such as the icon 634 is selected, the processor120 of the transmitting-side electronic device 101 may send a requestfor sharing of data corresponding to the sharing object to thereceiving-side electronic device 104.

For example, if the sharing object such as the Audio icon 638 isselected in FIG. 6E, the processor 120 of the transmitting-sideelectronic device 101 may send a request for sharing of data such asaudio streaming corresponding to the sharing object to thereceiving-side electronic device 104.

Next, in operations 424 and 426, the transmitting-side electronic device101 may receive a sharing acceptance for the data from thereceiving-side electronic device 104 through the call server 310. Inthis case, the receiving-side electronic device 104 may send a sharingacceptance message for the data to the call server 310, and the callserver 310 may send or forward the sharing acceptance message to thetransmitting-side electronic device 101.

For example, the receiving-side electronic device 104 may performsharing acceptance for the data in response to a detection of a touch onan Accept icon displayed on its display. For example, when sending arequest for sharing of the data to the receiving-side electronic device104, the transmitting-side electronic device 101 may display anotification 641 indicating that the transmitting-side electronic device101 is requesting sharing of the data, as shown in FIG. 7A. As shown inFIG. 7B, the receiving-side electronic device 104 may display an Accepticon 644 and a Reject icon 646 on its display. In this case, in responseto a detection of a touch on the Accept icon 644, the processor of thereceiving-side electronic device 104 may perform sharing acceptance forthe data. The processor of the receiving-side electronic device 104 maysend the sharing acceptance to the transmitting-side electronic device101.

Next, in operation 450, for the transmitting-side electronic device 101,its data session may be connected to the receiving-side electronicdevice 104. For example, in operation 430, the transmitting-sideelectronic device 101 may send a request for the data session to therelay server 300. In response to the data session request, the relayserver 300 may send a request for confirmation of the call status of thetransmitting-side electronic device 101 to the call server 310 inoperation 432. In response to the request, if the transmitting-sideelectronic device 101 is communicating with the receiving-sideelectronic device 104, the call server 310 may send a response for thecall status to the relay server 300 in operation 434. In operation 440,the receiving-side electronic device 104 may send a request for the datasession to the relay server 300. In response to the data sessionrequest, the relay server 300 may send a request for confirmation of thecall status of the receiving-side electronic device 104 to the callserver 310 in operation 442. In response to the request, if thereceiving-side electronic device 104 is communicating with thetransmitting-side electronic device 101, the call server 310 may send aresponse for the call status to the relay server 300 in operation 444.In operation 450, if the call status of the receiving-side electronicdevice 104 with the transmitting-side electronic device 101 isconfirmed, the relay server 300 may connect a data session between thetransmitting-side electronic device 101 and the receiving-sideelectronic device 104 through the call server 310.

Although the data session connection process is performed after thesharing request and sharing acceptance processes (operations 420 to 426)in FIG. 4, various exemplary embodiments of the present disclosure willnot be limited to the order assumed in FIG. 4.

Next, the transmitting-side electronic device 101 may transmit the datain real time to the receiving-side electronic device 104 to share thedata in real time. For example, in operation 460, the processor 120 ofthe transmitting-side electronic device 101 may receive an input for aselection of data to be shared. The processor 120 of thetransmitting-side electronic device 101 may transmit the selected datato the receiving-side electronic device 104. In this case, the processor120 of the transmitting-side electronic device 101 may transmit theselected data to the relay server 300 in operation 462, and the relayserver 300 may transmit the data to the receiving-side electronic device104 in operation 464. In operation 466, the processor of thereceiving-side electronic device 104 may store the received data in itsmemory, completing the data sharing.

For example, referring to FIGS. 8A-8C, the data may be audio streaming.In this case, as shown in FIG. 8A, the transmitting-side electronicdevice 101 may transmit the data such as the audio streaming (e.g., anaudio file named ‘Over the Horizon’) to the receiving-side electronicdevice 104 in real time. The transmitting-side electronic device 101 maydisplay a control window 650 for controlling the audio streaming. In thecontrol window 650 may be displayed an icon for playing the audiostreaming, an icon for stopping the audio streaming, or a bar indicatingthe playing time. As shown in FIG. 8B, the receiving-side electronicdevice 104 may receive the data such as the streaming audio, and playthe received data. The receiving-side electronic device 104 may displaya window 660 indicating reception of the data on a Phone Conversationscreen. In the window 660, indicating reception of the data, may bedisplayed the name of the streaming audio or the bar indicating theplaying time. As shown in FIG. 8C, the processor 120 of thetransmitting-side electronic device 101 may receive an input for aselection of data to be shared. For example, the processor 120 of thetransmitting-side electronic device 101 may display a menu on which oneof a plurality of audio streaming 670 can be selected by the user.

As another example, the data may be an image or video. In this case, thetransmitting-side electronic device 101 may transmit the image or videofile itself, transmit decoded data of the image or video in a streamingmanner, or capture a playback screen of the image or video and transmitthe captured playback screen. One of these transmission methods may beselected based on a user's input, or selected in the relay server 300.

Next, the transmitting-side electronic device 101 may execute thecontrol command related to the shared data in the same way as thereceiving-side electronic device 104. For example, in operation 500, thetransmitting-side electronic device 101 may receive an input for atransmitting-side control command by detecting a selection of a controlcommand icon included in a control window. In operation 501, thetransmitting-side electronic device 101 may execute thetransmitting-side control command. The transmitting-side electronicdevice 101 may send the transmitting-side control command to thereceiving-side electronic device 104. In this case, thetransmitting-side electronic device 101 may send the transmitting-sidecontrol command to the receiving-side electronic device 104 through therelay server 300 in operations 502 and 504. In operation 506, thereceiving-side electronic device 104 may execute the transmitting-sidecontrol command. On the contrary, the receiving-side electronic device104 may receive an input for a receiving-side control command bydetecting a selection of a control command icon included in a controlwindow in operation 510. In operation 511, the receiving-side electronicdevice 104 may execute the receiving-side control command. Thereceiving-side electronic device 104 may send the receiving-side controlcommand to the transmitting-side electronic device 101. In this case,the receiving-side electronic device 104 may send the receiving-sidecontrol command to the transmitting-side electronic device 101 throughthe relay server 300 in operations 512 and 514. In operation 516, thetransmitting-side electronic device 101 may execute the receiving-sidecontrol command.

Referring to FIGS. 9A to 11B, a description will be made of an exampleof a process in which the transmitting-side electronic device 101 andthe receiving-side electronic device 104 execute a control command forthe shared data in the same way. Referring to FIG. 9A, if the sharingobject such as the Internet icon 636 is selected, the processor 120 ofthe transmitting-side electronic device 101 may send a request forsharing of data such as the Internet URL corresponding to the sharingobject, to the receiving-side electronic device 104. If thetransmitting-side electronic device 101 sends the request for sharing ofdata to the receiving-side electronic device 104, the receiving-sideelectronic device 104 may display a notification 680 indicating that thetransmitting-side electronic device 101 is requesting sharing of thedata, as shown in FIG. 9B. As shown in FIG. 9C, the receiving-sideelectronic device 104 may display an Accept icon 684 and a Reject icon686 on its display. In response to a detection of a touch on the Accepticon 684, the processor of the receiving-side electronic device 104 mayperform sharing acceptance for the data. The processor of thereceiving-side electronic device 104 may send the sharing acceptance tothe transmitting-side electronic device 101. The transmitting-sideelectronic device 101 may transmit the data such as the Internet URL tothe receiving-side electronic device 104. As shown in FIG. 11A, thereceiving-side electronic device 104 may receive the data such as theInternet URL, and access the Internet URL (See 690).

In this case, the transmitting-side electronic device 101 may receive aninput for a transmitting-side control command by detecting a selectionof a control command icon included in a control window in operation 500.For example, the control command may be a Note command. As shown in FIG.10A, the transmitting-side electronic device 101 may display a controlwindow such as a Note window 681 on the display 150. The Note window 681may include a control command icon such as an Enter Notes icon 682. Thetransmitting-side electronic device 101 may receive an input for atransmitting-side control command such as a note input command bydetecting a selection of the Enter Notes icon 682 included in the Notewindow 681. The transmitting-side electronic device 101 may execute thetransmitting-side control command in operation 501. For example, asshown in FIG. 10B, the transmitting-side electronic device 101 mayexecute the transmitting-side control command such as the note inputcommand, and display a note 684. The transmitting-side electronic device101 may send the transmitting-side control command such as the noteinput command to the receiving-side electronic device 104. Thereceiving-side electronic device 104 may execute the transmitting-sidecontrol command. The note input command may be a command to capture ascreen of the note and transmit the captured screen, or a command totransmit only the change data (e.g., a change in note input coordinates)corresponding to the note. The note input command may be set by the useror the processor.

As shown in FIG. 11B, the receiving-side electronic device 104 mayexecute the transmitting-side control command such as the note inputcommand, and display a note 694. In addition, the receiving-sideelectronic device 104 may also receive an input for a receiving-sidecontrol command such as a note input command by detecting a selection ofan Enter Notes icon 692 included in a Note window 691. Similarly, thereceiving-side electronic device 104 may also send the receiving-sidecontrol command such as the note input command to the transmitting-sideelectronic device 101. The transmitting-side electronic device 101 mayexecute the receiving-side control command.

Referring to FIGS. 12A and 12B, as another example, thetransmitting-side control command may be a screen control command forcontrolling the Internet screen. The screen control command may be, forexample, a navigation command (Go Back, Go Forward, View Back and thelike) or a scroll command. As shown in FIG. 12A, the transmitting-sidecontrol command may be, for example, a scroll-down command 696 among thescreen commands. Therefore, if the transmitting-side control commandsuch as the scroll-down command is executed, the Internet screen may bescrolled down as shown in FIG. 12B. In this case, the transmitting-sideelectronic device 101 may send the transmitting-side control commandsuch as the scroll-down command to the receiving-side electronic device104. The receiving-side electronic device 104 may execute thetransmitting-side control command such as the scroll-down command, toscroll down the Internet screen in the same way as in FIG. 12B.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the transmitting-side electronic device can share the datacorresponding to the sharing object with the receiving-side electronicdevice during the voice call connection. In particular, in accordancewith an exemplary embodiment of the present disclosure, the sharingobject for the data sharing can be displayed on the Phone Conversationscreen. In accordance with an exemplary embodiment of the presentdisclosure, since the data can be shared during the voice callconnection, a separate connection process or execution of an applicationis not required. In accordance with an exemplary embodiment of thepresent disclosure, the transmitting-side electronic device may sharedata with the receiving-side electronic device with less datatransmission, compared with the high-data traffic scheme such as a videocall. In addition, in accordance with an exemplary embodiment of thepresent disclosure, the transmitting-side electronic device and thereceiving-side electronic device may share a control command.

FIG. 13 is a flowchart for a control method of data sharing electronicdevices according to another exemplary embodiment of the presentdisclosure. FIGS. 14A to 15C illustrate execution screens of datasharing electronic devices according to another exemplary embodiment ofthe present disclosure. The flowchart of FIG. 13 is the same as that ofFIG. 4 in terms of operations 400 to 450, so a description thereof willbe omitted. In accordance with another exemplary embodiment of thepresent disclosure, the transmitting-side electronic device may transmitthe data to the receiving-side electronic device in real time using anaddress corresponding to the data, which is generated in a contentserver, thereby sharing the data in real time.

Next, in operation 460, the processor 120 of the transmitting-sideelectronic device 101 may receive an input for a selection of data to beshared. In operation 470, the processor 120 of the transmitting-sideelectronic device 101 may transmit the selected data to a content server320. In operation 472, the content server 320 may generate an addresscorresponding to the data. In operation 474, the content server 320 maytransmit the address to the transmitting-side electronic device 101. Thetransmitting-side electronic device 101 may transmit the address to therelay server 300 in operation 476, and the relay server 300 may transmitthe address to the receiving-side electronic device 104 in operation478. In operation 480, the receiving-side electronic device 104 maytransmit the address to the content server 320 to request the data. Inoperation 482, the content server 320 may transmit the datacorresponding to the address to the receiving-side electronic device104. In operation 484, the receiving-side electronic device 104 mayreceive the data, completing the data sharing.

Reference will now be made to FIGS. 14A to 15C to describe anotherexemplary embodiment of the present disclosure. Upon detecting aselection of the Image icon 634 corresponding to the sharing object inFIG. 6E, the transmitting-side electronic device 101 may share datacorresponding to the image with the receiving-side electronic device104. In this case, the transmitting-side electronic device 101 mayreceive an input for a selection of the sharing object. In other words,as shown in FIGS. 14A and 14B, the transmitting-side electronic device101 may receive an input for a selection of one image 710 from among oneor more images 700.

In operation 470, the transmitting-side electronic device 101 maytransmit the image 710 to the content server 320. In operation 472, thecontent server 320 may generate an address corresponding to the image710. In operation 474, the content server 320 may transmit the addresscorresponding to the storage location of the image 710 in the contentserver to the transmitting-side electronic device 101. Thetransmitting-side electronic device 101 may transmit the address to therelay server 300 in operation 476, and the relay server 300 may transmitthe address to the receiving-side electronic device 104 in operation478. In operation 480, the receiving-side electronic device 104 maytransmit the address to the content server 320 to request data,specifically, the image 710. In operation 482, the content server 320may transmit the image 710 corresponding to the address to thereceiving-side electronic device 104. In operation 484, thereceiving-side electronic device 104 may receive the image 710,completing the data sharing. As shown in FIG. 14C, the receiving-sideelectronic device 104 may display the image 710 on its display. Inoperation 500, the transmitting-side electronic device 101 may receivethe control command such as the notes. For example, as shown in FIG.15A, the transmitting-side electronic device 101 may display a controlwindow such as a note window 720 on the display 150. The note window 720may include an icon for changing the color or thickness of a pen formaking notes on the display screen. The transmitting-side electronicdevice 101 may receive an input for a transmitting-side control commandsuch as a note input command. For example, the note input command mayinclude a command to change the position, color or thickness of the pen.Therefore, the transmitting-side electronic device 101 may send the noteinput command to the receiving-side electronic device 104. For example,if the transmitting-side electronic device 101 transmits a note inputcommand ‘Draw’ to the receiving-side electronic device 104 as shown inFIG. 15B, the note input command may be executed in the same way asshown in FIG. 15C.

FIG. 16 is a flowchart for a control method of data sharing electronicdevices according to further another exemplary embodiment of the presentdisclosure. In another exemplary embodiment of the present disclosureillustrated in FIG. 16, among one or more sharing objects, a sharingobject that a transmitting-side electronic device can share with areceiving-side electronic device can be displayed on the display. Theflowchart shown in FIG. 16 may include the same process as that of FIGS.4 and 5.

Referring to FIG. 16, in operation 740, the transmitting-side electronicdevice 101 may transmit information about the sharable application andcontent to the relay server 300. The information about the sharableapplication and content may mean information about the application andcontent that can be shared in the transmitting-side electronic device101.

For example, among an image application, an Internet application and anaudio application, the applications that can be shared in thetransmitting-side electronic device 101 may include the imageapplication and the Internet application. In this case, in operation740, the transmitting-side electronic device 101 may transmitinformation indicating that only the image of the image application andthe URL of the Internet application can be shared, to the relay server300. Upon receiving the information in operation 742, the receiving-sideelectronic device 104 may send a response to the transmission to therelays server 300 in operation 744. In this case, the application thatcan be shared in the receiving-side electronic device 104 may be theimage application. Then, in operation 744, the receiving-side electronicdevice 104 may transmit information indicating that only the image ofthe image application can be shared, to the relay server 300 as aresponse to the transmission. Since only the image of the imageapplication can be shared, the transmitting-side electronic device 101that has received the information may display only the sharing objectcorresponding to the image application on the display 150. Referringback to FIG. 6E, in this case, the transmitting-side electronic device101 may display on the display 150 only the Image icon 634 among theImage icon 634, the Internet icon 636 and the Audio icon 638. Thereceiving-side electronic device 104 may also display only the Imageicon 634 on its display.

FIGS. 17A to 22 illustrate execution screens of data sharing electronicdevices according to another exemplary embodiment of the presentdisclosure. In another exemplary embodiment of the present disclosureillustrated in FIGS. 17A to 22, the transmitting-side electronic device101 may receive a User's Contact image, a Call Connecting image, a PhoneConversation image, a Call Ending image or SNS profile stored in thereceiving-side electronic device 104, from an editing server, anddisplay the received image on the display 150.

The receiving-side electronic device 104 may transmit the User's Contactimage, the Call Connecting image, the Phone Conversation image, the CallEnding image or the SNS profile to the editing server. The editingserver may store in its memory the User's Contact image, the CallConnecting image, the Phone Conversation image, the Call Ending image,or the SNS profile. In response to the user of the receiving-sideelectronic device 104, the editing server may register the Contactimage, the Call Connecting image, the Phone Conversation image, the CallEnding image or the SNS profile.

In response to an operation by the user of the receiving-side electronicdevice 104, the transmitting-side electronic device 101 may receive theContact image, the Call Connecting image, the Phone Conversation image,the Call Ending image or the SNS profile from the editing server, andstore them in its memory. The transmitting-side electronic device 101may display the Contact image in the contact application. Thetransmitting-side electronic device 101 may display the Call Connectingimage on a Call Connecting screen of a phone application. Thetransmitting-side electronic device 101 may display the PhoneConversation image on a Phone Conversation screen of the phoneapplication. The transmitting-side electronic device 101 may display theCall Ending image on a Call Ended screen of the phone application. Thetransmitting-side electronic device 101 may display the SNS profile on aDial Input screen of the phone application or a screen of the contactapplication.

For example, as shown in FIG. 17A, the receiving-side electronic device104 may transmit a User's Contact image to the editing server toregister the image. FIG. 17A illustrates a screen 752 for registrationof user information in the editing server. For example, a Contact image758 may be registered for the user having a name ‘Michael Smith’ 756 anda phone number ‘+82 10-2160-5322’ of a user information tab 754. Inresponse to an operation by the user of the receiving-side electronicdevice 104, the transmitting-side electronic device 101 may receive theContact image 758 from the editing server, and store the received imagein its memory. As shown in FIG. 17B, the transmitting-side electronicdevice 101 may display the Contact image 758 for the user having thename ‘Michael Smith’ 756 and the phone number ‘+82 10-2160-5322’ in acontact application 762.

As another example, as shown in FIG. 18A, the receiving-side electronicdevice 104 may transmit a Call Connecting image of the user of thereceiving-side electronic device to the editing server to register theimage. FIG. 18A illustrates a screen 752 for registration in the editingserver. For example, a Call Connecting image 768 of a Dialing tab 766may be registered. In response to the user of the receiving-sideelectronic device 104, the transmitting-side electronic device 101 mayreceive the Call Connecting image 768 from the editing server, and storethe received image in its memory. As shown in FIG. 18B, thetransmitting-side electronic device 101 may display the Call Connectingimage 768 on the Call Connecting screen 770 of the phone application.

As another example, as shown in FIG. 19A, the receiving-side electronicdevice 104 may transmit a Phone Conversation image of the user to theediting server to register the image. FIG. 19A illustrates a screen 752for registration of contact information in the editing server. Forexample, a Phone Conversation image 776 of a Calling tab 774 may beregistered. In response to an operation by the user of thereceiving-side electronic device 104, the transmitting-side electronicdevice 101 may receive the Phone Conversation image 776 from the editingserver, and store the received image in its memory. As shown in FIG.19B, the transmitting-side electronic device 101 may display the PhoneConversation image 776 on a Call Ended screen 778 of the phoneapplication.

As another example, as shown in FIG. 20A, the receiving-side electronicdevice 104 may transmit a Call Ending image of the user to the editingserver to register the image. FIG. 20A illustrates a screen 752 forregistration in the editing server. For example, a Call Ending image 784of a Call-end tab 782 may be registered. In response to the user of thereceiving-side electronic device 104, the transmitting-side electronicdevice 101 may receive the Call Ending image 784 from the editingserver, and store the received image in its memory. As shown in FIG.20B, the transmitting-side electronic device 101 may display the CallEnding image 784 on a Call Ended screen 786 of the phone application.

As another example, as shown in FIG. 21A, the receiving-side electronicdevice 104 may transmit an SNS profile of the user of the receiving-sideelectronic device to the editing server to register the SNS profile.FIG. 21A illustrates a screen 752 for registration of user informationin the editing server. For example, the user may be registered in an SNStab 788. In response to an operation by the user of the receiving-sideelectronic device 104, the transmitting-side electronic device 101 mayreceive the SNS profile from the editing server, and store the receivedSNS profile in its memory. As shown in FIG. 21B, the transmitting-sideelectronic device 101 may display an SNS profile 792 on a Dial Inputscreen 790 of the phone application. As shown in FIG. 21C, thetransmitting-side electronic device 101 may display the SNS profile 792on a screen 794 of the contact application.

As another example, as shown in FIG. 22, the receiving-side electronicdevice 104 may enter an authoring tool 796 included in the editingserver, to perform user registration. The authoring tool 796 may includean item for inputting an ID 797 and a password 798. Therefore, theediting server may register only the user logged in (799) by receivingthe ID 797 and the password 798 in the authoring tool 796, to register aContact image of the registered user, a Call Connecting image, a PhoneConversation image, a Call Ending image or an SNS profile.

FIG. 23 is a block diagram 800 of an electronic device 801 according tovarious exemplary embodiments of the present disclosure. The electronicdevice 801 may configure, for example, the entirety or part of theelectronic device 101 shown in FIG. 1. Referring to FIG. 23, theelectronic device 801 may include at least one Application Processor(AP) 810, a communication module 820, a Subscriber Identification Module(SIM) card 824, a memory 830, a sensor module 840, an input device 850,a display 860, an interface 870, an audio module 880, a camera module891, a power management module 895, a battery 896, an indicator 897, anda motor 898.

The AP 810 may control a plurality of hardware or software componentsconnected to the AP 810 by driving the operating system or applicationprogram, and may process and compute a variety of data includingmultimedia data. The AP 810 may be implemented in, for example, Systemon Chip (SoC). In one exemplary embodiment, the AP 810 may furtherinclude a Graphic Processing Unit (GPU, not shown).

The communication module 820 (e.g., the communication interface 160) mayperform data transmission/reception in communication between theelectronic device 801 (e.g., the electronic device 101) and otherelectronic devices (e.g., the electronic device 104 or the server 106)connected thereto over the network. In one exemplary embodiment, thecommunication module 820 may include a cellular module 821, a WiFimodule 823, a BT module 825, a GPS module 827, an NFC module 828, and aRadio Frequency (RF) module 829.

The cellular module 821 may provide voice call, video call, textservice, Internet service, or the like over the network (e.g., LTE,LTE-A, CDMA, WCDMA, UMTS, WiBro, GSM, or the like). The cellular module821 may perform identification and authentication on the electronicdevices in the communication network using, for example, a subscriberidentification module (e.g., the SIM card 824). In one exemplaryembodiment, the cellular module 821 may perform at least some of thefunctions that the AP 810 can provide. For example, the cellular module821 may perform at least some of the multimedia control functions.

In one exemplary embodiment, the cellular module 821 may include aCommunication Processor (CP). The cellular module 821 may be implementedin, for example, SoC. Although components such as the cellular module821 (e.g., the CP), the memory 830 or the power management module 895are shown as components independent of the AP 810 in FIG. 23, the AP 810may be implemented to include at least some (e.g., the cellular module821) of the components according to one exemplary embodiment of thepresent disclosure.

In one exemplary embodiment, the AP 810 or the cellular module 821(e.g., the CP) may load, on a volatile memory, the command or datareceived from at least one of a non-volatile memory and other componentsconnected thereto, and process the loaded command or data. The AP 810 orthe cellular module 821 may store in a non-volatile memory the data thatis received from or generated by at least one of other components.

Each of the WiFi module 823, the BT module 825, the GPS module 827, orthe NFC module 828 may include, for example, a processor for processingthe data that is transmitted and received therethrough. Although thecellular module 821, the WiFi module 823, the BT module 825, the GPSmodule 827, or the NFC module 828 are shown as separate components inFIG. 23, at least some (e.g., two or more components) of the cellularmodule 821, the WiFi module 823, the BT module 825, the GPS module 827and the NFC module 828 may be incorporated into one Integrated Chip (IC)or IC package according to one exemplary embodiment of the presentdisclosure. For example, at least some (e.g., a CP corresponding to thecellular module 821 or a WiFi processor corresponding to the WiFi module823) of the processors corresponding to the cellular module 821, theWiFi module 823, the BT module 825, the GPS module 827 and the NFCmodule 828 may be implemented in one SoC.

The RF module 829 may transmit and receive data, for example, RFsignals. Although not shown, the RF module 829 may include, for example,a transceiver, a Power Amp Module (PAM), a frequency filter, a Low NoiseAmplifier (LNA), or the like. The RF module 829 may further includeparts (e.g., conductors or conducting wires) for transmitting andreceiving electromagnetic waves in the free space in wirelesscommunication. Although the cellular module 821, the WiFi module 823,the BT module 825, the GPS module 827 and the NFC module 828 are shownto share one RF module 829 with each other in FIG. 23, at least one ofthe cellular module 821, the WiFi module 823, the BT module 825, the GPSmodule 827 and the NFC module 828 may transmit and receive RF signalsthrough a separate RF module according to one exemplary embodiment ofthe present disclosure.

The SIM card 824 may be a subscriber identification module, and may beinserted into a slot that is formed in a specific position of theelectronic device. The SIM card 824 may include unique identificationinformation (e.g., an Integrated Circuit Card Identifier (ICCID)) orsubscriber information (e.g., an International Mobile SubscriberIdentity (IMSI)).

The memory 830 (e.g., the memory 130) may include an internal memory 832and an external memory 834. The internal memory 832 may include at leastone of, for example, a volatile memory (e.g., a dynamic RAM (DRAM), astatic RAM (SRAM), a synchronous dynamic RAM (SDRAM), or the like) and anon-volatile memory (e.g., an One Time Programmable ROM (OTPROM), aProgrammable ROM (PROM), an Erasable And Programmable ROM (EPROM), anElectrically Erasable And Programmable ROM (EEPROM), a mask ROM, a flashROM, a NAND flash memory, a NOR flash memory, or the like).

In one exemplary embodiment, the internal memory 832 may be a SolidState Drive (SSD). The external memory 834 may further include a flashdrive (e.g., Compact Flash (CF), Secure Digital (SD), Micro SecureDigital (Micro-SD), Mini Secure Digital (Mini-SD), and extreme Digital(xD)), or a memory stick. The external memory 834 may be functionallyconnected to the electronic device 801 through a variety of interfaces.In one exemplary embodiment, the electronic device 801 may furtherinclude a storage device (or storage media) such as a hard drive.

The sensor module 840 may measure a physical quantity or detect anoperating state of the electronic device 801, and convert the measuredor detected information into an electrical signal. The sensor module 840may include at least one of, for example, a gesture sensor 840A, a gyrosensor 840B, a pressure sensor 840C, a magnetic sensor 840D, anacceleration sensor 840E, a grip sensor 840F, a proximity sensor 840G, acolor sensor 840H (e.g., a Red/Green/Blue (RGB) sensor), a bio sensor840I, a temperature/humidity sensor 840J, an illuminance sensor 840K,and a Ultra Violet (UV) sensor 840M. Additionally or alternatively, thesensor module 840 may include, for example, an electronic noise (E-nose)sensor (not shown), an electromyography (EMG) sensor (not shown), anelectroencephalogram (EEG) sensor (not shown), an electrocardiogram(ECG) sensor (not shown), an Infra Red (IR) sensor (not shown), irissensor (not shown), a fingerprint sensor (not shown), or the like. Thesensor module 840 may further include a control circuit for controllingat least one of the sensors belonging thereto.

The input device 850 may include a touch panel 852, a (digital) pensensor 854, a key 856, or an ultrasonic input device 858. The touchpanel 852 may recognize a touch input in at least one of, for example,capacitive, resistive, infrared and ultrasonic ways. The touch panel 852may further include a control circuit. In the case of the capacitiveway, the touch panel 852 may recognize the physical contact or proximityof the user. The touch panel 852 may further include a tactile layer. Inthis case, the touch panel 852 may provide a tactile feedback to theuser.

The (digital) pen sensor 854 may be implemented by using, for example, amethod the same as or similar to receiving a user's touch input, or aseparate recognition sheet. The key 856 may include, for example, aphysical button, an optical key, or a keypad. The ultrasonic inputdevice 858 is a device that can determine data by detecting the soundwaves with a microphone (e.g., a microphone 888) in the electronicdevice 801, through an input tool that generates an ultrasonic signal,and this device enables wireless recognition. In one exemplaryembodiment, the electronic device 801 may receive a user input from anexternal electronic device (e.g., a computer or a server) connectedthereto using the communication module 820.

The display 860 (e.g., the display 150) may include a panel 862, ahologram device 864, or a projector 866. The panel 862 may be, forexample, a Liquid Crystal Display (LCD) panel, an Active-Matrix OrganicLight-Emitting Diode (AM-OLED) panel or the like. The panel 862 may beimplemented, for example, in a flexible, transparent or wearable manner.The panel 862 may be configured in one module together with the touchpanel 852. The hologram device 864 may show a stereoscopic image in theair using the interference of light. The projector 866 may display animage by projecting the light onto the screen. The screen may belocated, for example, inside or outside the electronic device 801. Inone exemplary embodiment, the display 860 may further include a controlcircuit for controlling the panel 862, the hologram device 864 or theprojector 866.

The interface 870 may include, for example, an HDMI 872, a USB 874, anoptical interface 876, or a D-subminiature (D-sub) 878. The interface870 may be incorporated, for example, into the communication interface160 shown in FIG. 1. Additionally or alternatively, the interface 870may include, for example, a Mobile High-Definition Link (MHL) interface,a Secure Digital (SD) card/Multi-Media Card (MMC) interface, or InfraredData Association (IrDA) interface.

The audio module 880 may convert sounds and electronic signals in atwo-way manner. At least some of the components of the audio module 880may be incorporated, for example, into the I/O interface 140 shown inFIG. 1. The audio module 880 may process sound information that is inputor output through, for example, a speaker 882, a receiver 884, anearphone 886, a microphone 888, or the like.

The camera module 891 is a device that can capture still images andvideos. In one exemplary embodiment, the camera module 891 may includeone or more image sensors (e.g., a front sensor or a rear sensor), alens (not shown), an Image Signal Processor (ISP, not shown), or a flash(e.g., an LED or xenon lamp, not shown).

The power management module 895 may manage the power of the electronicdevice 801. Although not shown, the power management module 895 mayinclude, for example, a Power Management Integrated Circuit (PMIC), acharger Integrated Circuit (IC), or a battery or fuel gauge.

The PMIC may be mounted, for example, in an IC or SoC semiconductor. Thecharging scheme can be classified into a wired charging scheme and awireless charging scheme. The charger IC may charge a battery, and mayprevent inflow of the over-voltage or over-current from the charger. Inone exemplary embodiment, the charger IC may include a charger IC for atleast one of the wired charging scheme and the wireless charging scheme.The wireless charging scheme may include, for example, a magneticresonance scheme, a magnetic induction scheme, an electromagnetic schemeor the like, and may further include additional circuits for wirelesscharging, e.g., a coil loop, a resonant circuit, a rectifier or thelike.

The battery gauge may measure, for example, the level, charging voltage,charging current or temperature of the battery 896. The battery 896 maystore or generate electricity, and may supply power to the electronicdevice 801 using the stored or generated electricity. The battery 896may include, for example, a rechargeable battery or a solar battery.

The indicator 897 may indicate a specific state (e.g., a boot state, amessage state, charging state or the like) of the electronic device 801or a part thereof (e.g., the AP 810). The motor 898 may convert anelectrical signal into mechanical vibrations. Although not shown, theelectronic device 801 may include a processing unit (e.g., a GPU) formobile TV support. The processing unit for mobile TV support may processmedia data based on the standards such as, for example, DigitalMultimedia Broadcasting (DMB), Digital Video Broadcasting (DVB), orMedia Flow.

Each of the above-described components of the electronic deviceaccording to various exemplary embodiments of the present disclosure maybe configured with one or more components or elements, and a name of thecomponent may vary depending on the type of the electronic device. Theelectronic device according to various exemplary embodiments of thepresent disclosure may be configured to include at least one of theabove-described components, and some of the components may be omitted,or the electronic device may include other additional components. Someof the components of the electronic device according to variousexemplary embodiments of the present disclosure may be configured as oneentity by being combined, so the entity may perform the same functionsof the components as those given before the combination.

FIG. 24 illustrates a communication protocol 900 between a plurality ofelectronic devices (e.g., an electronic device 910 and an electronicdevice 930) according to various exemplary embodiments of the presentdisclosure. Referring to FIG. 24, the communication protocol 900 mayinclude, for example, a device discovery protocol 951, a capabilityexchange protocol 953, a network protocol 955, and an applicationprotocol 957.

In one exemplary embodiment, the device discovery protocol 951 may be aprotocol by which electronic devices (e.g., the electronic device 910 orthe electronic device 930) can detect an external electronic device thatcan communicate with the electronic devices, or connect with thedetected external electronic device. For example, the electronic device910 (e.g., the electronic device 101) may detect the electronic device930 (e.g., the electronic device 104) as a device that can communicatewith the electronic device 910, through a communication method (e.g.,WiFi, BT, USB or the like) available in the electronic device 910, usingthe device discovery protocol 951. The electronic device 910 may obtainand store identification information about the detected electronicdevice 930 using the device discovery protocol 951, for thecommunication connection with the electronic device 930. The electronicdevice 910 may establish a communication connection with the electronicdevice 930 based on, for example, at least the identificationinformation.

In certain exemplary embodiments, the device discovery protocol 951 maybe a protocol for mutual authentication between a plurality ofelectronic devices. For example, the electronic device 910 may performauthentication between the electronic device 910 and the electronicdevice 930 based on communication information (e.g., a Media AccessControl (MAC) address, a Universally Unique Identifier (UUID), aSubsystem Identification (SSID), and Information Provider (IP) address)for a connection with at least the electronic device 930.

In one exemplary embodiment, the capability exchange protocol 953 may bea protocol for exchanging information related to the function of theservice supportable in at least one of the electronic device 910 and theelectronic device 930. For example, the electronic device 910 and theelectronic device 930 may exchange with each other the informationrelated to the function of the service that is currently provided byeach of them, using the capability exchange protocol 953. Theexchangeable information may include identification informationindicating a specific service among a plurality of services supportablein the electronic device 310 and the electronic device 320. For example,the electronic device 910 may receive identification information for aspecific service provided by the electronic device 930, from theelectronic device 930 using the capability exchange protocol 953. Inthis case, based on the received identification information, theelectronic device 910 may determine whether the electronic device 910can support the specific service.

In one exemplary embodiment, the network protocol 955 may be a protocolfor controlling a flow of the data that is, for example, transmitted andreceived to provide linked services, between the electronic devices(e.g., the electronic device 910 and the electronic device 930) that areconnected to enable communication. For example, at least one of theelectronic device 910 and the electronic device 930 may perform errorcontrol or data quality control using the network protocol 955.Additionally or alternatively, the network protocol 955 may determine atransport format of the data that is transmitted and received betweenthe electronic device 910 and the electronic device 930. At least one ofthe electronic device 910 and the electronic device 930 may manage(e.g., connect or terminate) at least one session for mutual dataexchange using the network protocol 955.

In one exemplary embodiment, the application protocol 957 may be aprotocol for providing a procedure or information, which is forexchanging data related to the service provided to the externalelectronic device. For example, the electronic device 910 (e.g., theelectronic device 101) may provide a service to the electronic device930 (e.g., the electronic device 104 or the server 106) using theapplication protocol 957.

In one exemplary embodiment, the communication protocol 900 may includea standard communication protocol, a communication protocol (e.g., acommunication protocol specified by a communication device manufactureror a network provider itself) specified by an individual or anorganization, or a combination thereof.

FIG. 25 illustrates devices that are connected in a control method ofelectronic devices having a function of sharing content in voicecommunication according to an exemplary embodiment of the presentdisclosure. Referring to FIG. 25, a first electronic device 2500, asecond electronic device 2520, an operator communication network 2530, aSession Initiation Protocol-Application Server (SIP-AS) 2540, a MediaServer (MS) 2560, or a Web Content Server (WCS) 2550 may be connected tothe mobile network.

FIGS. 26A and 26B are flowcharts for a control method of an electronicdevice having a function of sharing content in voice communicationaccording to an exemplary embodiment of the present disclosure. FIGS.27A to 30B illustrate execution screens of an electronic device having afunction of sharing content in voice communication according to anexemplary embodiment of the present disclosure. Reference will be madeto FIGS. 27A to 30B to describe an exemplary embodiment of the presentdisclosure.

Referring to FIGS. 26A and 26B, in operations 2610 to 2614, theelectronic device 2500 having a function of sharing content in voicecommunication according to an exemplary embodiment of the presentdisclosure may transmit a call over the mobile network. A processor ofthe electronic device 2500 may request the MS 2560 to drive an AutomaticResponse System (ARS) system, by sending a call over the mobile network.

More specifically, in operation 2610, the processor may send a call tothe operator communication network 2530 over the mobile network. Themobile network may include an Evolved Node B (ENB), a Home SubscriberServer (HSS), and a Call Session Control Function (CSCF). The ENB maymean a communication repeater for enabling a User Equipment (UE) toaccess a packet network. The HSS may mean a network user information andIP management server for determining unique information of a UE andassigning an IP thereto. The CSCF may mean a connection controller fortransmitting information about call origination to a recipient uponreceiving a request for call origination from a UE. In other words, theelectronic device 2500 may send a call to the operator communicationnetwork 2530 including the ENB, HSS and CSCF, using the communicationinterface.

In this case, the processor may send a call by running a phoneapplication. For example, as shown in FIG. 27A, the processor mayexecute a phone application 2700. The processor may display an executionscreen of the phone application 2700 on a display. The phone application2700 may include dial numbers (or digits) 2710. The display may beformed as a touch screen, but is not limited thereto. The processor mayreceive an input by detecting a touch on the touch screen. Therefore,the processor may receive an input of a phone number by detectingtouches on the dial numbers 2710 on the touch screen. For example, asshown in FIG. 27B, the processor may receive an input of a phone number2720 such as ‘15881234’. The processor may extract, from a memory, aname of a contact corresponding to the phone number 2720 such as‘15881234’, and display the extracted name. The memory may include adatabase containing a name and a phone number associated with thecontact. For example, as shown in FIG. 27B, the processor may display,as ‘GalaxyEX’ 2730, a name of the contact corresponding to the phonenumber 2720 such as ‘15881234’. The processor may send a call byreceiving an input for a selection of a Send Call icon 2740.

Next, in operation 2612, the operator communication network 2530 maysend an access request to the ARS to the SIP-AS 2540. The SIP-AS 2540may receive the access request to the ARS from the operatorcommunication network 2530. The SIP-AS 2540 may perform communicationwith the operator communication network 2530, as the SIP-AS 2540 isconnected to the mobile network. The operator communication network 2530may send an access request to the ARS, including data for the phonenumber, to the SIP-AS 2540.

Next, in operation 2614, the SIP-AS 2540 may send a request for drivingthe ARS to the MS 2560. In this case, the MS 2560 may performcommunication with the SIP-AS 2540, as the MS 2560 is connected to themobile network. The SIP-AS 2540 may send a request for driving the ARSto the MS 2560 of the operator corresponding to the received phonenumber. In other words, the SIP-AS 2540 may store a database regardingthe operator corresponding to each of the phone numbers. The SIP-AS 2540may extract, from the database, information about the MS 2560 of anoperator corresponding to the phone number. The SIP-AS 2540 may send arequest for driving the ARS to the extracted MS 2560.

For example, as shown in FIG. 27B, the SIP-AS 2540 may extract, from thedatabase, information about the MS 2560 of the operator corresponding tothe phone number such as ‘15881234’. If the operator corresponding to‘15881234’ is ‘GalaxyEX’, the SIP-AS 2540 may send a request for drivingthe ARS to the MS 2560 for ‘GalaxyEX’. Thereafter, in operation 2630,the ARS may be connected between the electronic device 2500 and the MS2560 for ‘GalaxyEX’. For example, the operator corresponding to the‘GalaxyEX’ may provide the ARS related to a delivery service (or acourier service). The ARS may provide, by voice, contents such as, forexample, viewing of information regarding the delivery of goods orproviding of details regarding the delivery.

Next, in operation 2620, the electronic device 2500 may transmit acalled number (or a called ID) to the WCS 2550. The processor of theelectronic device 2500 may transmit the called number to the WCS 2550.The WCS 2550 may be connected to the mobile network to performcommunication with the electronic device 2500. Therefore, the WCS 2550may receive the called number from the electronic device 2500. Thecalled number may mean a phone number that the electronic device 2500has received from the user. For example, the called number maycorrespond to the phone number ‘15881234’ in FIG. 27B.

Next, in operation 2622, the WCS 2550 may query the called number. TheWCS 2550 may query an operator corresponding to the called number. TheWCS 2550 may store in its memory a database regarding an operatorcorresponding to each of the phone numbers. Therefore, the WCS 2550 mayreceive, from the database, information on an operator corresponding tothe called number received from the electronic device 2500.

For example, as shown in FIG. 27B, if the called number that the WCS2550 has received from the electronic device 2500 is ‘15881234’, the WCS2550 may query, as ‘GalaxyEX’, the operator corresponding to the callednumber ‘15881234’ from the database.

Next, in operation 2624, the WCS 2550 may invoke content of the operatorcorresponding to the called number. The WCS 2550 may store the contentof the operator corresponding to the called number in a database.Therefore, the WCS 2550 may invoke the content of the operator based onthe called number. As for the content of the operator, the WCS 2550 mayhave the content registered in advance by the operator, and store theregistered content in the database. For example, the content may be anadvertising image of the operator, or an item or menu provided by theARS. As shown in the example of FIGS. 28A to 28C, if the operatorprovides a delivery service, the content may be an advertising image forthe delivery service, or an item or menu that is related to the deliveryservice and provided by the ARS. The item or menu provided by the ARSmay be, for example, a menu for viewing delivery goods information, anitem for goods information, or an item for the delivery process.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, there is no need to sign up for a separate service procedureor undergo an authentication process, to receive the content of theoperator. In other words, in accordance with an exemplary embodiment ofthe present disclosure, it is possible to directly invoke the content ofthe operator based on the called number.

Next, in operation 2626, the electronic device 2500 may receive thecontent from the WCS 2550. The WCS 2550 may transmit the invoked contentto the electronic device 2500. In other words, the electronic device2500 according to an exemplary embodiment of the present disclosure mayreceive the content to be shared from the WCS 2550.

For example, the content may be an advertising image of the operator, oran item or menu provided by the ARS. As shown in the example of FIGS.27A and 27B, if the operator provides a delivery service, the contentmay be an advertising image for the delivery service, or an item or menuthat is related to the delivery service and provided by the ARS. Thecontent may be an image, an icon, an item or a menu, in addition to thevoice.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive content other thanthe voice from the WCS 2550 in the ARS, and share the received content.In other words, in accordance with an exemplary embodiment of thepresent disclosure, the electronic device 2500 may receive the contentfrom the WCS 2550, and visually provide images, icons, items or menustogether with the voice to the user who uses the ARS.

Next, in operation 2628, the electronic device 2500 may display thecontent received from the WCS 2550 on its display. In other words, theprocessor of the electronic device 2500 may display the content receivedfrom the WCS 2550 on its display.

For example, as shown in FIG. 28A, if the content received from the WCS2550 is an advertising image 2810 to be displayed on a Call Send Standbyscreen, the processor of the electronic device 2500 may display theadvertising image 2810 on the Call Send Standby screen. Therefore, theelectronic device 2500 may provide the content such as the advertisingimage together with the voice to the user who uses the ARS.

In addition, as shown in FIG. 28B, the processor of the electronicdevice 2500 may display an icon, an item or a menu 2820 to 2860 providedby the ARS on the display. For example, the processor of the electronicdevice 2500 may display an item or menu that is related to the deliveryservice and provided by the ARS. In other words, the processor maydisplay a menu 2820 for viewing information regarding the delivery ofgoods, an item regarding a name (e.g., ‘GalaxyEx’) of the operatorproviding the delivery service, an item 2840 for goods information suchas ‘Samsung Galaxy Gear 1 Pkg From Amazon $299 Track #1234567890’, anitem 2850 for indicating the delivery process such as ‘Dec 10 11:58AM/Arrival Scan Heathrow Airport, UK’, and a Map icon 2860 for showingthe delivery process.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive the content such asan advertising image, an item or a menu, other than the voice from theARS or an Interactive Voice Response (IVR) system, and display thereceived content. The content such as an advertising image, an item or amenu may correspond to the data that the operator has registered in adatabase in advance. Therefore, the operator providing the ARS or IVRservice may register the content such as an advertising image, an itemor a menu in the WCS 2550 in advance, to display the content on theelectronic device 2500.

Next, in operation 2630, the ARS may be connected between the electronicdevice 2500 and the MS 2560. The MS 2560 may mean a server that providesthe ARS service to the electronic device 2500. In response to the ARSdrive request 2614, the MS 2560 may connect a voice call to theelectronic device 2500 and provide the ARS service thereto using thevoice call. The MS 2560 may mean a server that provides an IVR voiceafter connecting the voice call to the electronic device 2500. The IVRmay mean a service for sharing interactive data between the electronicdevice 2500 and the MS 2560. For example, the IVR may provide a DualTone Multiple Frequency (DTMF) service. The DTMF means a signal havingtwo frequency components, may mean a dial tone (or voice) that isgenerated when a dial button is pressed. In other words, the DTMFservice may mean a service in which a server decodes the generated dialtone (or voice) to provide the ARS service.

For example, as shown in FIGS. 27A and 27B, if the operatorcorresponding to the called number ‘15881234’ is ‘GalaxyEX’, the ARS maybe connected between the electronic device 2500 and the MS 2560 for‘GalaxyEX’.

Although operation 2630 is performed after operations 2620 to 2628 asshown in FIG. 26A, operation 2630 may be performed before operations2620 to 2628. Therefore, operation 2630 is not limited to the orderdescribed in FIGS. 26A and 26B.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may provide the content otherthan voice from the WCS 2550, while providing the ARS voice using, forexample, the DTMF service from the MS 2560.

Next, in operation 2640, the electronic device 2500 may receive an inputfor a selection of an item. The processor of the electronic device 2500may receive an input for a selection of an item. For example, thedisplay of the electronic device 2500 may be formed as a touch screen,and may receive an input for a selection of an item from the touchscreen. In other words, as shown in FIG. 28B, the processor of theelectronic device 2500 may receive an input for a selection of an item,such as the Map icon 2860 for showing the delivery process.

Next, in operation 2642, the electronic device 2500 may transmit theselected item to the WCS 2550. In other words, the processor of theelectronic device 2500 may transmit the selected item to the WCS 2550over the mobile network. For example, as shown in FIG. 28B, theprocessor of the electronic device 2500 may transmit the selected itemsuch as the Map icon 2860 for showing the delivery process, to the WCS2550.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may transmit the selected item tothe ARS system corresponding to the WCS 2550. In other words, theelectronic device 2500 may perform two-way mutual datatransmission/reception with the ARS system corresponding to the WCS2550. Therefore, in accordance with an exemplary embodiment of thepresent disclosure, the electronic device 2500 may perform two-waymutual data transmission/reception, instead of unilaterally receivingdata from the ARS system or the IVR system.

Next, in operation 2644, the WCS 2550 may reflect the received selecteditem. In other words, the WCS 2550 may extract the content in which theWCS 2550 reflected the item that was selected in the electronic device2500. For example, as shown in FIG. 28B, if the selected itemcorresponds to the Map icon 2860 which shows the delivery process, theWCS 2550 may extract the reflected content such as the Map image inwhich a closer image of the delivery process is shown.

Next, in operation 2646, the electronic device 2500 may receive thereflected content from the WCS 2550. In other words, the processor ofthe electronic device 2500 may receive the reflected content from theWCS 2550 over the mobile network. For example, the electronic device2500 may receive the reflected content such as a Map image in which thedelivery process is shown, from the WCS 2550.

Next, in operation 2648, the electronic device 2500 may display thereflected content received from the WCS 2550, on its display. In otherwords, the processor of the electronic device 2500 may display thereflected content received from the WCS 2550, on its display.

For example, as shown in FIG. 28C, the electronic device 2500 maydisplay the reflected content such as the Map image in which thedelivery process is shown, on its display. The electronic device 2500may display a Map image 2870 showing the delivery process from ‘HeathrowAirport, UK’ to ‘Barcelona, Spain’.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive the reflected controlfrom the WCS 2550 in the ARS or IVR service. In other words, inaccordance with an exemplary embodiment of the present disclosure,during the ARS service, the electronic device 2500 may not only receivethe content other than the voice content, but also continuously receivethe reflected content from the WCS 2550. Therefore, in accordance withan exemplary embodiment of the present disclosure, the ARS system maynot only just provide the voice content of the users, but may alsoprovide the visual content to the user, so the user may receive the ARSservice, while viewing the visual content such as an image, an item or amenu.

Next, in operation 2650, the electronic device 2500 may receive thevoice corresponding to the situation or the displayed content from theMS 2560 in real time. The MS 2560 may transmit the data pertaining tothe voice corresponding to the displayed content to the electronicdevice 2500 in real time. In other words, the MS 2560 may transmit thedata regarding the voice needed for the ARS service to the electronicdevice 2500 in real time. The MS 2560 may transmit the data regardingthe voice corresponding to the displayed content to the electronicdevice 2500 in real time. The displayed content may be changed in realtime in the ARS service. The situation may correspond to the contenttransmitted by the WCS 2550. The situation may correspond to the contentthat is reflected in the WCS 2550.

For example, referring to FIG. 28A, the situation may correspond to theadvertising image 2810 on the Call Send Standby screen corresponding tothe content transmitted by the WCS 2550. The MS 2560 may transmit thevoice content corresponding to the displayed content (e.g., the voiceadvertising GalaxyEx) to the electronic device 2500. Therefore, theelectronic device 2500 may provide the voice advertising GalaxyEx to theuser, in response to the process of displaying the advertising image2810 on the Call Send Standby screen.

As shown in FIG. 28B, the situation may correspond to the icon, item ormenu 2820 to 2860 provided by the ARS system regarding the deliveryservice corresponding to the content transmitted by the WCS 2550. Inthis case, the MS 2560 may transmit, to the electronic device 2500, thevoice content related to the displayed content (e.g., “This is GalaxyExpress. You can check the delivery status of the goods you haveordered, on the screen”) corresponding to the situation. Therefore, theelectronic device 2500 may provide the voice explaining the icon, itemor menu 2820 to 2860 to the user, in response to the process ofdisplaying the icon, item or menu 2820 to 2860 provided by the ARSsystem regarding the delivery service.

As shown in FIG. 28C, the situation may correspond to the Map image 2870in which the delivery process corresponding to the content that isreflected in the WCS 2550 is shown. The MS 2560 may transmit, to theelectronic device 2500, a voice message (e.g., “You have entered theDelivery Details screen. Please check the location and expected arrivaltime of the goods on the map provided on the screen”) corresponding tothe displayed situation. Therefore, the electronic device 2500 mayprovide, to the user, the voice corresponding to the content that isreflected in the WCS 2550.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive in real time the dataregarding the voice needed for the ARS service from the MS 2560. Inparticular, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive, from the MS 2560,the voice corresponding to the content transmitted from the WCS 2550 orthe content reflected in the WCS 2550.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may receive not only the voice inthe ARS system but also the content from the WCS 2550, and may receivethe voice corresponding to the content from the MS 2560. In other words,in accordance with an exemplary embodiment of the present disclosure,the electronic device 2500 may implement the ARS system that can providethe visual content and the voice at the same time.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, when providing the ARS service, the electronic device 2500does not need to run a separate application or use a video calloperation which requires an excessive amount of datatransmission/reception, to receive the content.

Next, in operation 2660, the electronic device 2500 may receiveconfirmed service data from the WCS 2550. The WCS 2550 may confirm theservice data. The WCS 2550 may transmit the confirmed service data tothe electronic device 2500. The confirmed service data may be theservice that is finally confirmed in the ARS service. In particular, theconfirmed service data may include the content that is reflected inoperations 2640 to 2646.

For example, in FIGS. 27A to 28C, the ARS service regarding the deliveryservice is provided. The WCS 2550 may confirm the final deliveryschedule as the confirmed service data. For example, the final deliveryschedule may be ‘Estimated Arrival: Dec. 12, 2013 12:00 PM’. Therefore,the WCS 2550 may confirm the final delivery schedule such as ‘EstimatedArrival: Dec. 12, 2013 12:00 PM’ as the confirmed service data. The WCS2550 may transmit the confirmed service data such as ‘Estimated Arrival:Dec. 12, 2013 12:00 PM’ to the electronic device 2500.

Next, in operation 2662, the electronic device 2500 may display theconfirmed service data received from the WCS 2550 on its display. Theelectronic device 2500 may display the confirmed service data on a CallEnded screen. The electronic device 2500 may display the confirmedservice data on a preset application. For example, the presetapplication may be a log application (or a Recent Log View application).

For example, in the ARS service regarding the delivery service, theconfirmed service data may be the final delivery schedule. The confirmedservice data corresponding to the final delivery schedule may be‘Estimated Arrival: Dec. 12, 2013 12:00 PM’. Therefore, as shown in FIG.29A, the processor of the electronic device 2500 may display ‘EstimatedArrival: Dec. 12, 2013 12:00 PM’ 2930 corresponding to the confirmedservice data on the Call Ended screen 2910. In addition, the processormay display even an advertising image 2920 of the operator on the CallEnded screen 2910. As shown in FIG. 29B, the Call Ended screen may beterminated after a lapse of a preset time, and an initial screen of thephone application may then be displayed.

As another example, as shown in FIG. 30A, the processor of theelectronic device 2500 may display ‘Estimated Arrival: Dec. 12, 201312:00 PM’ corresponding to the confirmed service data, on the presetapplication. For example, the preset application may be a logapplication. Therefore, as shown in FIG. 30A, if the log application3000 is executed, then the processor of the electronic device 2500 maydisplay a call log 3010 for the terminated ARS service call. As shown inFIG. 30B, if the call log 3010 is selected, the processor may display‘Estimated Arrival: Dec. 12, 2013 12:00 PM’ 3030 corresponding to theconfirmed service data.

Therefore, in accordance with an exemplary embodiment of the presentdisclosure, the electronic device 2500 may display the confirmed servicedata received from the WCS 2550 on its display. In accordance with anexemplary embodiment of the present disclosure, even after the ARSservice call is terminated, the electronic device 2500 may display theconfirmed service data even on the Call End screen or the presetapplication such as the log application, so the user can check again theconfirmed service data. In addition, in accordance with an exemplaryembodiment of the present disclosure, before and during the call, theelectronic device 2500 may receive content from the WCS 2550, transmitthe selected item to the WCS 2550, and receive the reflected contentfrom the WCS 2550, so the ARS system can organically operate with eachother.

FIG. 26B is a flowchart which illustrates a control method of anelectronic device having a function of sharing content during voicecommunication according to an exemplary embodiment of the presentdisclosure. In one exemplary embodiment, the content sharing may beperformed between the electronic device 2500 and a small businesselectronic device 2504. The small business electronic device 2504 maybe, for example, a Media Server (MS).

In operation 2671, the electronic device 2500 may run the phoneapplication. In operation 2672, the electronic device 2500 may send aservice subscription and authentication request to a subscriber server2502. In operation 2673, the subscriber server 2502 may send asubscription confirmation response (or authentication) to the electronicdevice 2500.

In operation 2674, the electronic device 2500 may perform a dialingoperation. In operation 2675, the electronic device 2500 may send avoice call connection request to an IP Multimedia Subsystem (IMS)network 2501. In operation 2676, the IMS network 2501 may send the voicecall connection request to the small business electronic device 2504.Accordingly, in operation 2677, the electronic device 2500 may connect avoice call to the small business electronic device 2504.

In operation 2678, the small business electronic device 2504 may run aphone application. In operation 2679, the small business electronicdevice 2504 may send a service subscription and authentication requestto the subscriber server 2502. In operation 2680, the small businesselectronic device 2504 may receive a subscription confirmation response(or authentication) from the subscriber server 2502. In operation 2681,the small business electronic device 2504 may send a data sessionrequest to a relay server 2503. In operation 2682, the relay server 2503may generate a receiving-side data session to the small businesselectronic device 2504. In operation 2683, the relay server 2503 maytransmit screen configuration information to the small businesselectronic device 2504. In operation 2684, the small business electronicdevice 2504 may configure a menu screen based on the received screenconfiguration information. In operation 2685, the small businesselectronic device 2504 may select a Sync button. In operation 2686, thesmall business electronic device 2504 may send a data session request tothe IMS network 2501. In operation 2689, the relay server 2503 maygenerate a user-side data session to the electronic device 2500.Accordingly, the electronic device 2500 and the small businesselectronic device 2504 may establish a data session with each other. Ifthe small business electronic device 2504 performs menu manipulation inoperation 2691, the small business electronic device 2504 may transmitthe data to the relay server 2503 in operation 2692. The relay server2503 may transmit the received data to the electronic device 2500 inoperation 2693.

FIG. 31 is a flowchart illustrating a control method of electronicdevices having a function of sharing content during voice communicationaccording to another exemplary embodiment of the present disclosure.FIGS. 32 to 35 illustrate execution screens of electronic devices havinga function of sharing content during voice communication according toanother exemplary embodiment of the present disclosure. Reference willbe made to FIGS. 31 to 35 to describe another exemplary embodiment ofthe present disclosure.

Referring to FIG. 31, an electronic device 2500 having a function ofsharing content in voice communication according to another exemplaryembodiment of the present disclosure may first perform operations 2610to 2630 described in FIG. 26A in the same way. Therefore, in anotherexemplary embodiment of the present disclosure, a description ofoperations 2610 to 2630 will be omitted. In addition, the electronicdevice 2500 described in FIGS. 26A and 26B will be referred to as afirst electronic device.

An example of execution screens for operations 2610 to 2630 in FIG. 26A,which are repeated in another exemplary embodiment of the presentdisclosure, will be first described with reference to FIGS. 32A to 32C.For example, referring to FIG. 32A, a processor of the first electronicdevice 2500 may run a phone application. The processor may receive aphone number by detecting touches on dial numbers (or digits) 3210 onthe touch screen. For example, as shown in FIG. 32A, the processor mayreceive a phone number 3220 such as ‘15886789’. The processor maydisplay, as ‘PizzaARS’ 3230, a name of the contact corresponding to thephone number 3220 such as ‘15886789’. The processor may receive an inputfor a selection of a Send Call icon 3240 and send a call (in operation2610 in FIG. 26A). The operator communication network 2530 may send anARS access request to the SIP-AS 2540 (in operation 2612 in FIG. 26A).The SIP-AS 2540 may send an ARS drive request to the MS 2560 (inoperation 2614 in FIG. 26A). If the operator corresponding to the phonenumber ‘15885678’ is ‘PizzaARS’, the SIP-AS 2540 may send an ARS driverequest to the MS 2560 for ‘PizzaARS’. The first electronic device 2500may transmit a called number to the WCS 2550 (in operation 2620 in FIG.26A). The WCS 2550 may query the called number (in operation 2622 inFIG. 26A). The WCS 2550 may query, as ‘PizzaARS’, the operatorcorresponding to the called number ‘15885678’ from the database. The WCS2550 may invoke content of the operator corresponding to the callednumber (in operation 2624 in FIG. 26A). If the operator provides a pizzadelivery service, the content may be an advertising image for the pizzadelivery service, or an item or menu provided by the ARS systemregarding the pizza delivery service. The first electronic device 2500may receive the content from the WCS 2550 (in operation 2626 in FIG.26A). The first electronic device 2500 may display the content receivedfrom the WCS 2550 on its display (in operation 2628 in FIG. 26A). Asshown in FIG. 32B, if the content received from the WCS 2550 is anadvertising image to be displayed on the Call Send Standby screen, theprocessor of the first electronic device 2500 may display theadvertising image 3250 on the Call Send Standby screen. The ARS may beconnected between the first electronic device 2500 and the MS 2560 (inoperation 2630 in FIG. 26A). For example, as shown in FIG. 32A, if theoperator corresponding to the phone number ‘15885678’ is ‘PizzaARS’, theARS may be connected between the first electronic device 2500 and the MS2560 for ‘PizzaARS’.

Next, in operation 3132, the first electronic device 2500 may send arequest for a voice call connection to the second electronic device 2520to the WCS 2550. In other words, the first electronic device 2500 maysend a request for a voice call connection to the second electronicdevice 2520 through the WCS 2550 during the ARS. The second electronicdevice 2520 may mean an electronic device of the operator providing theARS. Therefore, the first electronic device 2500 may directly execute avoice call with the operator providing the ARS.

For example, as shown in FIG. 32C, the processor of the first electronicdevice 2500 may display an ARS Entry screen on its display. Theprocessor may display an icon 3262 for entering a simple ARS order, anicon 3264 for entering an interactive order to receive the content whileperforming a voice call with the operator, and an icon 3266 for making areference to the existing order. In this case, if the icon for enteringan interactive order is selected, the processor may perform operations3134 to 3139. For example, if the icon 3264 for entering an interactiveorder is selected in FIG. 32C, the processor may perform operations 3134to 3139. In this case, the first electronic device 2500 may repeatoperation 2628 in FIG. 26A to display the content received from the WCS2550 on the display. For example, as shown in FIG. 34, the firstelectronic device 2500 may display the content such as an item or menu3470 provided to the pizza delivery service, on its display.

However, if the icon 3262 for entering a simple ARS order is selected,the processor may run only the ARS system. For example, if the icon 3262for entering a simple ARS order is selected in FIG. 33A, the processormay run only the ARS system to send a call to the ARS system as shown inFIG. 33B.

However, if the icon 3266 for making a reference to the existing orderis selected, the processor may display details of the existing order.For example, if an icon 3566 for making a reference to the existingorder is selected as shown in FIG. 35A, the processor may displaydetails 3568 of the existing order as shown in FIG. 35B.

Next, in operation 3134, the WCS 2550 may send a connection request fora voice call to the second electronic device 2520. In other words, theWCS 2550 may send a connection request for a voice call to the secondelectronic device 2520, in response to the voice call connection requestfrom the first electronic device 2500.

Next, in operation 3136, if the second electronic device 2520 acceptsthe connection of a voice call with the first electronic device 2500 inresponse to the request from the WCS 2550, the second electronic device2520 may proceed to operation 3138 and its succeeding operations.However, if the second electronic device 2520 does not accept theconnection of a voice call with the first electronic device 2500, thesecond electronic device 2520 may terminate the call connection process.

Next, in operation 3138, the WCS 2550 may transmit the content, whichwas invoked in operation 2624, to the second electronic device 2520. Inother words, the WCS 2550 has transmitted the content invoked inoperation 2624 to the first electronic device 2500 in operation 2626. Inthis case, the WCS 2550 may transmit the content invoked in operation2624 even to the second electronic device 2520 in the same way.Therefore, the first electronic device 2500 and the second electronicdevice 2520 may receive the same content from the WCS 2550, sharing thecontent.

For example, as shown in FIG. 34, the first electronic device 2500 mayreceive the content such as the item or menu 3470 provided to the pizzadelivery service from the WCS 2550. The second electronic device 2520may also receive the content such as the item or menu 3470 provided tothe pizza delivery service from the WCS 2550 in the same way. Therefore,the first electronic device 2500 and the second electronic device 2520may share the same content such as the item or menu 3470 provided to thepizza delivery service.

Therefore, in accordance with another exemplary embodiment of thepresent disclosure, the first electronic device 2500 and the secondelectronic device 2520 may share the image content other than the voicecontent in the ARS system. In this case, in accordance with anotherexemplary embodiment of the present disclosure, there is no need to runa separate application or undergo an authentication procedure to sharethe content.

Next, in operation 3139, the voice call may be connected between thefirst electronic device 2500 and the second electronic device 2520. Ifthe second electronic device 2520 accepted the connection request thatwas made by the WCS 2550 in operation 3134, the voice call may beconnected between the first electronic device 2500 and the secondelectronic device 2520.

Therefore, in accordance with another exemplary embodiment of thepresent disclosure, the first electronic device 2500 may share the imagecontent other than the voice content while performing a voice call withthe operator corresponding to the second electronic device 2520, in theARS service. For example, as shown in the example of FIG. 34, a customerusing the first electronic device 2500 may visually see the item or menu3470 provided to the pizza delivery service, which is shown in FIG. 34,while performing a voice call with a counseling staff of the pizzadelivery service operator corresponding to the second electronic device2520, in the ARS system providing the pizza delivery service. Therefore,in accordance with another exemplary embodiment of the presentdisclosure, the customer may proceed with counseling (or make an order),viewing the content provided from the WCS 2550, while performing a voicecall with the counseling staff of the operator providing the ARS.

Next, in operation 3142, the first electronic device 2500 may transmit afirst selected item 3140 to the WCS 2550. In other words, the firstselected item 3140 that is selected in the first electronic device 2500may be transmitted to the WCS 2550.

For example, as shown in FIG. 34, an item such as ‘Side Dish’ may beselected. If the user wants to order a side dish, the item such as ‘SideDish’ may be selected. In this case, the first electronic device 2500may transmit ‘Side Dish’ corresponding to the first selected item to theWCS 2550.

Next, in operation 3144, the WCS 2550 may reflect the first selecteditem. For example, if the item such as ‘Side Dish’ is the first selecteditem, the WCS 2550 may reflect the menu in which ‘Side Dish’ isdisplayed, as first reflected content.

Next, in operation 3146, the WCS 2550 may transmit the first reflectedcontent to the first electronic device 2500. In operation 3147, the WCS2550 may transmit the first reflected content even to the secondelectronic device 2520. Therefore, the first reflected content may betransmitted to both of the first electronic device 2500 and the secondelectronic device 2520, to be shared.

Next, in operation 3148, the processor of the first electronic device2500 may drive a screen for displaying the first reflected content onthe display. For example, the first electronic device 2500 may display,on its display, the first reflected content such as the menu in which‘Side Dish’ is displayed in operation 3146. In addition, in operation3149, the processor of the second electronic device 2520 may also drivea screen for displaying the first reflected content on the display ofthe second electronic device 2520.

Next, in operation 3157, the first electronic device 2500 may receive,from the WCS 2550, second reflected content in which a second selecteditem that is selected in the second electronic device 2520 is reflected.

Next, in operation 3152, the second electronic device 2520 may transmita second selected item 3150 to the WCS 2550. In other words, the secondselected item 3150 that is selected in the second electronic device 2520may be transmitted to the WCS 2550. Next, in operation 3154, the WCS2550 may reflect the second selected item 3150. Next, in operation 3156,the WCS 2550 may transmit the second reflected content to the secondelectronic device 2520. In operation 3157, the WCS 2550 may transmit thesecond reflected content even to the first electronic device 2500.Therefore, the second reflected content may be transmitted to both ofthe first electronic device 2500 and the second electronic device 2520,to be shared.

Next, the electronic device 2500 having a function of sharing content invoice communication according to another exemplary embodiment of thepresent disclosure may perform operations 2640 to 2662 described in FIG.26A in the same way. Therefore, in another exemplary embodiment of thepresent disclosure, a description of operations 2640 to 2662 will beomitted.

Therefore, in accordance with another exemplary embodiment of thepresent disclosure, the user of the first electronic device 2500 mayperform a voice call with a counseling staff of the operatorcorresponding to the second electronic device 2520, even while using theARS system. In addition, since the first electronic device 2500 and thesecond electronic device 2520 can share the content from the WCS 2550,the user (or customer) of the first electronic device 2500 may share theitem selected by the user himself/herself, with the user (or counselingstaff) of the second electronic device 2520. Therefore, in accordancewith another exemplary embodiment of the present disclosure, the usermay receive counseling, while sharing the visually displayed contentwith the counseling staff in the ARS system.

FIG. 36 is a flowchart for a control method of an electronic devicehaving a function of sharing content in voice communication according tofurther another exemplary embodiment of the present disclosure. FIGS. 37to 42 illustrate execution screens of an electronic device having afunction of sharing content in voice communication according to furtheranother exemplary embodiment of the present disclosure. Reference willbe made to FIGS. 36 to 42 to describe further another exemplaryembodiment of the present disclosure.

Referring to FIG. 36, in the control method of an electronic devicehaving a function of sharing content in voice communication according tofurther another exemplary embodiment of the present disclosure, theelectronic device 2500 may first search for a dialed number in operation3600. A processor of the electronic device 2500 may search for thedialed from a database stored in the memory.

For example, referring to FIG. 37A, the processor may receive an inputfor a command to start a dialed search. For example, the command tostart a dialed search may be a dialed number which is input to access aspecific service name. In other words, the dialed inputted number may be‘74992’, digits of which correspond to the dial numbers corresponding toalphabetical characters for ‘pizza’. Therefore, the processor may searchfor a telephone number pertaining to a pizza delivery company from adatabase stored in the memory, in response to the numbers ‘74992’corresponding to the dialed numbers. In this case, the processor maydisplay the telephone number associated with the searched dialed numbersuch as ‘15886789’ on the display, as shown in FIG. 37A.

Next, in operation 3602, the electronic device 2500 may send a requestfor dial information to the SIP-AS 2540. The processor of the electronicdevice 2500 may receive an input for a command to request the dialinformation from the SIP-AS 2540. For example, as shown in FIG. 37A, theprocessor may receive an input for the command by detecting a selectionof an icon 3730 for executing the command. In other words, if aselection of the icon 3730 is detected, the processor may request dialinformation from the SIP-AS 2540.

Next, in operation 3604, the SIP-AS 2540 may extract dial information.The SIP-AS 2540 may extract dial information from the database stored inthe memory. The memory embedded in the SIP-AS 2540 may store thedatabase having the dial information. The database may store dialinformation that is stored in advance by each of a plurality ofoperators providing the ARS. For example, as shown in FIG. 37B, dialinformation such as Pizzahome (Ser. No. 15/886,789), Pizzahouse (Ser.No. 12/136,567), Housepizza (Ser. No. 12/136,568), Streetpizza (Ser. No.12/136,569) and Bestpizza (Ser. No. 12/136,572), may be stored inadvance in the database that is stored in the memory of the SIP-AS 2540.Therefore, the SIP-AS 2540 may extract the dial information from thedatabase stored in its memory.

Next, in operation 3606, the electronic device 2500 may receive theextracted dial information from the SIP-AS 2540. The SIP-AS 2540 maytransmit the dial information extracted from the database stored itsmemory, to the electronic device 2500. The processor of the electronicdevice 2500 may display the received dial information 3740 on thedisplay as shown in FIG. 37B.

Next, in operation 3608, the electronic device 2500 may receive couponinformation from the SIP-AS 2540. The SIP-AS 2540 may extract the couponinformation from the database stored in its memory. The memory embeddedin the SIP-AS 2540 may store the database having the coupon information.The database may store coupon information that is stored in advance byeach of a plurality of operators providing the ARS. The SIP-AS 2540 maytransmit the coupon information extracted from the database to theelectronic device 2500. The processor of the electronic device 2500 maydisplay the received coupon information 3770 as shown in FIG. 37C. FIG.37C shows a coupon 3770 provided by an operator ‘Housepizza’.

Next, in operation 3609, the electronic device 2500 may receive aselection of a decision to use the coupon. The electronic device 2500may receive an input for a command to determine use of the coupon. Forexample, the command may be a selection of an icon for determining useof the coupon. Referring to FIG. 37C, if a selection of an icon 3780 fordetermining use of the coupon is entered, the electronic device 2500 mayreceive a selection of a decision to use the coupon.

Next, the electronic device 2500 having a function of sharing content invoice communication according to further another exemplary embodiment ofthe present disclosure may perform operations 2610 to 2630 described inFIG. 26A in the same way. Therefore, in another exemplary embodiment ofthe present disclosure, a description of operations 2610 to 2630 will beomitted. An example of execution screens for operations 2610 to 2630 inFIG. 26A, which are repeated in another exemplary embodiment of thepresent disclosure, will be described with reference to FIGS. 38A to38C. For example, referring to FIG. 38A, the electronic device 2500 maysend a call with a phone number ‘15886789’ corresponding to‘Housepizza’. The electronic device 2500 may be connected to the ARSsystem corresponding to ‘Housepizza’ through the MS 2560. The electronicdevice 2500 may receive content corresponding to ‘Housepizza’ from theWCS 2550. The electronic device 2500 may transmit a selection 3800 of anitem for ordering ‘Hawaiian pizza’ to the WCS 2550.

Next, in operation 3632, the electronic device 2500 may transmitinformation about the determined coupon to the WCS 2550. For example, asshown in FIG. 37C, the electronic device 2500 may transmit, to the WCS2550, information about the coupon determined as ‘Hawaiian pizza 15%Discount Coupon’ 3770 of ‘Housepizza’.

Next, in operation 3634, the WCS 2550 may reflect the coupon. In otherwords, the WCS 2550 may calculate the final settlement price that isdetermined by reflecting the coupon with respect to the order price. Forexample, as shown in FIG. 38C, the WCS 2550 may calculate the finalsettlement price 3820 by reflecting the coupon 3810 with respect to theordered pizza ‘Hawaiian pizza’.

Next, in operation 3636, the electronic device 2500 may receive anotification regarding the reflection of the coupon from the WCS 2550.For example, as shown in FIG. 38C, the electronic device 2500 mayreceive, from the WCS 2550, a notification such as an image in which thefinal settlement price 3820 is displayed by reflecting the coupon 3810with respect to the ordered pizza ‘Hawaiian pizza’.

Next, the electronic device 2500 having a function of sharing content invoice communication according to another exemplary embodiment of thepresent disclosure may perform operations 2640 to 2662 described in FIG.26A in the same way. Therefore, in yet another exemplary embodiment ofthe present disclosure, a description of operations 2640 to 2662 will beomitted. An example of execution screens for operations 2640 to 2662 inFIG. 26A, which are repeated in another exemplary embodiment of thepresent disclosure, will be described with reference to FIGS. 39A and39B. For example, referring to FIG. 39A, if the order is completed, thecall may be terminated. The electronic device 2500 may receive confirmedservice data from the WCS 2550 (in operation 2660 in FIG. 26A). Forexample, as shown in FIG. 39B, the confirmed service data from the WCS2550 may be a delivery schedule. In this case, the electronic device2500 may display the delivery schedule 3930 on the Call End screen asshown in FIG. 39B.

Therefore, in accordance with another exemplary embodiment of thepresent disclosure, the electronic device 2500 may receive the dialedinformation of the operator providing the service that the electronicdevice 2500 desires to use, from the SIP-AS 2540. In addition, inaccordance with another exemplary embodiment of the present disclosure,the electronic device 2500 may receive the coupon information for theservice from the WCS 2550 and use the coupon in the ARS system.

FIGS. 40 to 42 illustrate execution screens of an electronic devicehaving a function of sharing content in voice communication according toanother exemplary embodiment of the present disclosure. Reference willbe made to FIGS. 26 and 40A to 42B to describe another exemplaryembodiment of the present disclosure.

Referring to FIG. 26A, first, in operations 2610 to 2614, the electronicdevice 2500 having a function of sharing content during voicecommunications according to another exemplary embodiment of the presentdisclosure may transmit a call over the mobile network. The processor ofthe electronic device 2500 may connect a request for driving the ARS tothe MS 2560 by transmitting a call over the mobile network. In thiscase, the processor may transmit a call by running a phone application.For example, as shown in FIG. 40A, the processor may transmit a call byrunning a phone application 4000. For example, as shown in FIG. 40B, theprocessor may receive a phone number 4010 such as ‘15886789’. Theprocessor may extract a name of a contact corresponding to the phonenumber 4010 such as ‘15886789’, from the memory, and display theextracted name. The memory may include a database having a name and aphone number associated with the contact. For example, as shown in FIG.40B, the processor may display, as ‘Pi Airlines’ 4020, a name of thecontact corresponding to the phone number 4010 such as ‘15886789’. Theprocessor may send a call upon receiving an input for a selection of aSend Call icon 4030.

Next, in operation 2612, the operator communication network 2530 maysend an access request for the ARS to the SIP-AS 2540.

Next, in operation 2614, the SIP-AS 2540 may send a request for drivingthe ARS to the MS 2560. For example, as shown in FIG. 40B, the SIP-AS2540 may extract information about the MS 2560 of the operatorcorresponding to the phone number such as ‘15886789’, from the database.If the operator corresponding to the phone number ‘15886789’ is ‘PiAirlines’, the SIP-AS 2540 may send a request for driving the ARS to theMS 2560 for ‘Pi Airlines’.

Next, in operation 2620, the electronic device 2500 may transmit thecalled number to the WCS 2550.

Next, in operation 2622, the WCS 2550 may query the called number. Forexample, as shown in FIG. 40B, if the called number that the WCS 2550has received from the electronic device 2500 is ‘15886789’, the WCS 2550may query, as ‘Pi Airlines’, the operator corresponding to the callednumber ‘15886789’ from the database.

Next, in operation 2624, the WCS 2550 may invoke content of the operatorcorresponding to the called number. For example, the content may be anadvertising image of the operator, or an item or menu provided by theARS.

Next, in operation 2626, the electronic device 2500 may receive thecontent from the WCS 2550.

Next, in operation 2628, the electronic device 2500 may display thecontent received from the WCS 2550 on its display. For example, as shownin FIG. 40C, if the content received from the WCS 2550 is an advertisingimage to be displayed on the Call Send Standby screen, the processor ofthe electronic device 2500 may display the advertising image 4040 on theCall Send Standby screen. In addition, as shown in FIG. 41A, theprocessor may display an item or menu 4150 provided by the ARS regardingan air ticket booking service.

Next, in operation 2630, the ARS may be connected between the electronicdevice 2500 and the MS 2560. For example, if the operator correspondingto the phone number ‘15885678’ is ‘Pi Airlines’, the ARS may beconnected between the electronic device 2500 and the MS 2560 for ‘PiAirlines’.

Next, in operation 2640, the electronic device 2500 may receive an inputfor a selection of an item. For example, as shown in FIG. 41A, theprocessor of the electronic device 2500 may receive an input for aselection 4160 (e.g., for selecting Barcelona at Departure) of adetailed item for air ticket booking.

Next, in operation 2642, the electronic device 2500 may transmit theselected item to the WCS 2550.

Next, in operation 2644, the WCS 2550 may reflect the received selecteditem. For example, the WCS 2550 may reflect a booking schedule in whichthe detailed item for air ticket booking is reflected.

Next, in operation 2646, the electronic device 2500 may receive thereflected content from the WCS 2550. For example, the electronic device2520 may receive the booking schedule in which the detailed item for airticket booking is reflected, from the WCS 2550.

Next, in operation 2648, the electronic device 2500 may display thereflected content received from the WCS 2550, on its display. Forexample, as shown in FIG. 41B, the processor of the electronic device2500 may display, on the display, the booking schedule 4170, which isfrom the WCS 2550 and in which the detailed item for air ticket bookingis reflected.

Next, in operation 2650, the electronic device 2500 may receive thevoice content corresponding to the displayed content from the MS 2560 inreal time.

Next, in operation 2660, the electronic device 2500 may receive theconfirmed service data from the WCS 2550. For example, the WCS 2550 mayconfirm the booking schedule in which the detailed item for air ticketbooking is reflected, and transmit the confirmed booking schedule to theelectronic device 2500.

Next, in operation 2662, the electronic device 2500 may display theconfirmed service data received from the WCS 2550 on its display. Forexample, as shown in FIG. 41C, the electronic device 2500 may displaythe confirmed air ticket 4180 corresponding to the confirmed dataservice received from the WCS 2550 on the Call Ended screen. Inaddition, as shown in FIG. 42B, the electronic device 2500 may displaythe confirmed air tickets 4295 included in the schedule in a Plannerapplication 4290 that is executed in FIG. 42A.

FIGS. 43A and 43B are flowcharts illustrating a control method ofelectronic devices having a function of sharing content during voicecommunications according to another exemplary embodiment of the presentdisclosure. FIGS. 44 to 48 illustrate execution screens of electronicdevices having a function of sharing content during voice communicationsaccording to another exemplary embodiment of the present disclosure. Inaccordance with another exemplary embodiment of the present disclosure,a voice call requested by a first electronic device may be connected toa second electronic device. During execution of the voice call, datacommunication may be performed with the first electronic device inresponse to a communication request for data transmission by the secondelectronic device. The second electronic device may request the WCS toprovide some of the content received from the WCS through the datacommunication, on a screen of the first electronic device.

Referring to FIG. 43, in operation 4310, the first electronic device2500 having a function of sharing content during voice communicationsaccording to another exemplary embodiment of the present disclosure maysend a connection request for connecting a voice call with the secondelectronic device 2520 to the operator communication network 2530. Thesecond electronic device 2520 may be an electronic device of an operatorproviding a service. Therefore, the first electronic device 2500 mayrequest a direct voice call connection with the operator providing theservice. For example, as shown in FIG. 44A, the processor of the firstelectronic device 2500 may request a connection of the voice call byrunning a phone application 4400.

Next, in operation 4312, the operator communication network 2530 maysend a connection request for the voice call to the SIP-AS 2540. Next,in operation 4314, the SIP-AS 2540 may send the connection request forthe voice call to the second electronic device 2520.

Next, in operation 4316, the second electronic device 2520 may acceptthe connection in response to the connection request for the voice call.For example, as shown in FIG. 44B, the second electronic device 2520 mayrun a phone application 4410 to detect a selection of a Connect Callicon 4420, and accept the connection. Therefore, in operation 4317, thevoice call may be connected between the first electronic device 2500 andthe second electronic device 2520, in response to the connectionacceptance by the second electronic device 2520.

Next, in operation 4318, the second electronic device 2520 may receivecontent of the operator from the WCS 2550. The WCS 2550 may store thecontent of the operator in its database. For example, the content may bean item or menu provided in the ARS system of the operator. For example,if the operator provides a pizza delivery service, the content may be apizza delivery menu. For example, as shown in FIG. 45B, the secondelectronic device 2520 may receive the content such as a pizza deliverymenu 4520 from the WCS 2550, and display the received content on itsdisplay. In this case, the first electronic device 2500 may display aPhone Conversation screen on its display, as shown in FIG. 45A.

Next, in operation 4320, the second electronic device 2520 may receivean input for a selection of content sharing. The selection of contentsharing may mean that the second electronic device 2520 shares thecontent received from the WCS 2550 with the first electronic device2500. For example, the selection of content sharing may mean that thesecond electronic device 2520 shares the received content such as thepizza delivery menu 4520, with the first electronic device 2500.

In this case, the second electronic device 2520 may receive the inputfor a selection of content sharing by detecting a selection of a ShareContent icon. For example, the second electronic device 2520 may receivethe input for a selection of content sharing by detecting a selection ofa Share Content icon such as ‘Sync’ 4630, as shown in FIG. 46A.

Next, in operation 4322, upon receiving the input for a selection ofcontent sharing, the second electronic device 2520 may send a contentsharing request to the WCS 2550. Next, in operation 4324, the WCS 2550may transmit the content to the first electronic device 2500 in responseto the content sharing request. For example, the WCS 2550 may transmitthe content such as a pizza delivery menu 4620 to the first electronicdevice 2500 in response to the content sharing request. In operation4340, the first electronic device 2500 may display the content such asthe pizza delivery menu 4620 on its display, as shown in FIG. 46B. Asanother example, the second electronic device 2520 may share editedcontent with the first electronic device 2500. The edited content maymean the content that is important to the user of the first electronicdevice 2500, who is a user of the service. The edited content may beedited by the second electronic device 2520. For example, as shown inFIG. 46C, the second electronic device 2520 may share the edited contentsuch as a pizza list (or a user's completed order list) 4640 with thefirst electronic device 2500.

Therefore, in accordance with another exemplary embodiment of thepresent disclosure, while a user of a service performs a voice call withan operator providing the service, if the operator selects an icon toshare content related to the service, the user may immediately recognizethe content on the screen. In other words, in accordance with anotherexemplary embodiment of the present disclosure, if the user has anyquestions about the service while performing a voice call with theoperator, the operator may share the content related to the service withthe user, solving the questions, so the user may correctly recognizedetails of the service. In addition, in accordance with anotherexemplary embodiment of the present disclosure, since the operatorrequests content sharing, the operator may pay a fee for datatransmission related to the content sharing.

Next, in operation 4342, the first electronic device 2500 may transmit afirst selected item 4340 to the WCS 2550. In other words, the firstselected item 4340 selected in the first electronic device 2500 may betransmitted to the WCS 2550. For example, as shown in FIG. 47A, thefirst selected item may be a pizza delivery payment item 4550.

Next, in operation 4344, the WCS 2550 may reflect the first selecteditem. For example, as shown in FIG. 47A, the WCS 2550 may reflect thefirst selected item such as the pizza delivery payment item 4550,completing the payment for the pizza delivery.

Next, in operation 4346, the WCS 2550 may transmit the first reflectedcontent to the first electronic device 2500. For example, the WCS 2550may transmit the first reflected content such as the pizza deliverypayment completion to the first electronic device 2500. In operation4347, the WCS 2550 may transmit the first reflected content even to thesecond electronic device 2520. Therefore, the first reflected contentmay be transmitted to both of the first electronic device 2500 and thesecond electronic device 2520, to be shared. For example, the firstreflected content such as the pizza delivery payment completion may betransmitted to both of the first electronic device 2500 and the secondelectronic device 2520, to be shared.

Next, in operation 4348, the processor of the first electronic device2500 may drive a screen for displaying the first reflected content onthe display. For example, as shown in FIG. 47B, the processor of thefirst electronic device 2500 may display the first reflected content4560 such as the pizza delivery payment completion, on its display. Inaddition, in operation 4349, the processor of the second electronicdevice 2520 may also drive a screen for displaying the first reflectedcontent on the display of the second electronic device 2520. Forexample, as shown in FIG. 47C, the processor of the second electronicdevice 2520 may display the first reflected content 4562 such as thepizza delivery payment completion, on its display.

Next, in operation 4352, the second electronic device 2520 may transmita second selected item 4350 to the WCS 2550. In other words, the secondselected item 4350 selected in the second electronic device 2520 may betransmitted to the WCS 2550. Next, in operation 4354, the WCS 2550 mayreflect the second selected item. Next, in operation 4356, the WCS 2550may transmit the second reflected content to the second electronicdevice 2520. In operation 4357, the WCS 2550 may transmit the secondreflected content even to the first electronic device 2500. Therefore,the second reflected content may be transmitted to both of the firstelectronic device 2500 and the second electronic device 2520, to beshared. Next, in operation 4357, the first electronic device 2500 mayreceive, from the WCS 2550, the second reflected content in which thesecond selected item selected in the second electronic device 2520 isreflected.

Next, in operation 4360, the second electronic device 2520 may receivean input for a selection of call termination. If the call termination isselected, the second electronic device 2520 may send a call terminationrequest to the WCS 2550 in operation 4362. In operation 4364, the voicecall between the first electronic device 2500 and the second electronicdevice 2520 may be terminated in response to the call terminationrequest.

Next, in operation 4370, the first electronic device 2500 may receiveconfirmed service data from the WCS 2550. For example, the WCS 2550 maytransmit the confirmed service data such as the pizza delivery paymentcompletion to the first electronic device 2500.

Next, in operation 4372, the first electronic device 2500 may displaythe confirmed service data received from the WCS 2550 on its display.For example, as shown in FIG. 48A, the first electronic device 2500displays the confirmed service data 4570 such as the pizza deliverypayment completion, received from the WCS 2550, on its display. Inaddition, as shown in FIG. 48B, the second electronic device 2520 mayalso receive the confirmed service data 4580 such as the pizza deliverypayment completion from the WCS 2550, and display the received data onits display.

In accordance with another exemplary embodiment of the presentdisclosure, the data sharing method may include an operation ofconnecting a voice channel with a phone number invoked from a firstelectronic device to perform a voice call with a second electronicdevice; and an operation of, during the voice call, performing datacommunication with the first electronic device in response to a datachannel establishment request from the second electronic device. Thesecond electronic device may request the server to provide some or allof the content received from the server over the data channel to thefirst electronic device.

FIG. 49 is a flowchart of a data sharing method according to variousexemplary embodiments of the present disclosure.

In operation 4910, a transmitting-side electronic device may obtain asharing object. More specifically, the transmitting-side electronicdevice may display a graphic user interface including at least oneobject. In particular, the transmitting-side electronic device mayconnect a voice call with a receiving-side electronic device. Thetransmitting-side electronic device may display a graphic user interfacethat includes a voice call connection screen and at least one object.The transmitting-side electronic device may obtain a sharing objectbased on an input through the graphic user interface.

In operation 4920, the transmitting-side electronic device may transmitdata corresponding to the obtained sharing object to the receiving-sideelectronic device. The transmitting-side electronic device may run asharing application corresponding to the sharing object. The sharingapplication may output data. The data may be based on a first format.The sharing application may be set to output data of the first format.The first format may be a format that is defined in common to both ofthe transmitting-side electronic device and the receiving-sideelectronic device. More specifically, an application stored in thereceiving-side electronic device may also process data of the firstformat. For example, if the sharing application is a map application,the data output from the map application may be coordinate information.The receiving-side electronic device may receive the coordinateinformation, and process and display the received coordinateinformation. An example of the first format may include user information(e.g., address book information), image information, URL, publictransport information, movie, time, text, alarm, applicationinformation, goods information, bank information, price, weather,barcode, Wi-Fi, control, sketch, touch, coordinate information, and thelike.

The transmitting-side electronic device may transmit the data to thereceiving-side electronic device through a data session. Thetransmitting-side electronic device may generate a data session based onthe information related to the connected voice call. For example, thetransmitting-side electronic device may generate a data session based onat least one of a called number and callee information, and a detaileddescription thereof will be given below. In addition, the receiving-sideelectronic device may also generate a data session based on theinformation related to the connected voice call. For example, thereceiving-side electronic device may generate a data session based on atleast one of a caller number and caller information, and a detaileddescription thereof will be given below.

FIG. 50 is a flowchart of a data sharing method according to variousexemplary embodiments of the present disclosure. The data sharing methodin FIG. 50 will be described in more detail with reference to FIGS. 51Ato 60. FIGS. 51A to 60 illustrate screens displayed by atransmitting-side electronic device and a receiving-side electronicdevice according to various exemplary embodiments of the presentdisclosure.

In operation 5010, a transmitting-side electronic device 5000 may obtainan object to be shared. FIG. 51A illustrates a screen displayed by thetransmitting-side electronic device 5000 according to an exemplaryembodiment of the present disclosure. As shown in FIG. 51A, thetransmitting-side electronic device 5000 may display a phone applicationexecution screen 5130 including at least one of a called number andcallee information. The transmitting-side electronic device 5000 mayfurther display an object panel 5132. A plurality of sharing objects5134, 5136, 5137, 5138 and 5139 may be arranged on the object panel5132. As described above, the transmitting-side electronic device 5000may connect a voice call to a receiving-side electronic device 5060.Accordingly, as shown in FIG. 51B, the receiving-side electronic device5060 may also display a phone application execution screen 5140. Thereceiving-side electronic device 5060 may further display an objectpanel 5142. A plurality of sharing objects 5144, 5146, 5147, 5148 and5149 may be arranged on the object panel 5142.

As shown in FIG. 52A, a user 1 of the transmitting-side electronicdevice 5000 may enter a command to designate the sharing object 5137that the user 1 desires to share. The transmitting-side electronicdevice 5000 may obtain a sharing object based on the entered command. Inthe example of FIG. 52A, it will be assumed that the transmitting-sideelectronic device 5000 has obtained a map-related sharing object 5137.

Referring back to FIG. 50, in operation 5015, the transmitting-sideelectronic device 5000 may send a sharing request to the receiving-sideelectronic device 5060 based on the obtained sharing object.

In operation 5020, the receiving-side electronic device 5060 may obtaina sharing acceptance in response to the received sharing request. Morespecifically, as shown in FIG. 52B, the receiving-side electronic device5060 may display a graphic user interface 5150 for querying whether toaccept sharing. The graphic user interface 5150 for querying whether toaccept sharing may include a region 5151 corresponding to ‘Accept’ and aregion 5152 corresponding to ‘Reject’. The user of the receiving-sideelectronic device 5060 may designate, for example, the region 5151corresponding to ‘Accept’, and the receiving-side electronic device 5060may obtain a sharing acceptance in response to the entered designation.

In operation 5030, the receiving-side electronic device 5060 may sendthe obtained sharing acceptance to the transmitting-side electronicdevice 5000.

In operation 5035, the transmitting-side electronic device 5000 mayexecute a sharing application. The sharing application may be anapplication corresponding to the sharing object. As described above, inone embodiment, the sharing object may be a map-related sharing object,and the transmitting-side electronic device 5000 may display a mapapplication as shown in FIG. 53A. In FIG. 53A, a map applicationexecution screen 5310 may include one or more function keys 5311 to 5315and a map.

In operation 5040, the receiving-side electronic device 5060 may executea sharing application. The sharing application may be an applicationcorresponding to the sharing object. As described above, in oneexemplary embodiment, the sharing object may be a map-related sharingobject, and the receiving-side electronic device 5060 may display a mapapplication as shown in FIG. 53B. In FIG. 53B, a map applicationexecution screen 5320 may include one or more function keys 5321 to 5325and a map.

In one exemplary embodiment, the map application executed by thetransmitting-side electronic device 5000 may be the same as the mapapplication executed by the receiving-side electronic device 5060. Inanother exemplary embodiment, the map application executed by thetransmitting-side electronic device 5000 may be different from the mapapplication executed by the receiving-side electronic device 5060. Morespecifically, the map application executed by the transmitting-sideelectronic device 5000 and the map application executed by thereceiving-side electronic device 5060 may be produced by differentmanufacturers. Even if the map application executed by thetransmitting-side electronic device 5000 is different from the mapapplication executed by the receiving-side electronic device 5060, themap application executed by the transmitting-side electronic device 5000and the map application executed by the receiving-side electronic device5060 may be produced based on the data sharing platform according to anexemplary embodiment of the present disclosure. Accordingly, the dataoutput from the map application executed by the transmitting-sideelectronic device 5000 and the data output from the map applicationexecuted by the receiving-side electronic device 5060 may be based onthe same format (e.g., the first format). For example, the data outputfrom the map application executed by the transmitting-side electronicdevice 5000 may be coordinate information, and the data output from themap application executed by the receiving-side electronic device 5060may also be coordinate information. Accordingly, even if the mapapplication executed by the transmitting-side electronic device 5000 isdifferent from the map application executed by the receiving-sideelectronic device 5060, the map application executed by thereceiving-side electronic device 5060 may process the coordinateinformation or the data output from the map application executed by thetransmitting-side electronic device 5000.

In operation 5045, the transmitting-side electronic device 5000 mayobtain data to be shared. For example, as shown in FIG. 54A, thetransmitting-side electronic device 5000 may receive an input todesignate the current location indication function key 5311 from theuser 1. The transmitting-side electronic device 5000 may display thecurrent location 5316 of the transmitting-side electronic device 5000 onthe map in response to the received input to designate the currentlocation indication function key 5311. The transmitting-side electronicdevice 5000 may obtain the current location of the transmitting-sideelectronic device 5000, as sharing data. The transmitting-sideelectronic device 5000 may directly obtain the data output from thesharing application (e.g., the map application), as sharing data, or mayobtain sharing data based on an additional sharing data designationcommand.

In operation 5050, the transmitting-side electronic device 5000 maytransmit the obtained sharing data to the receiving-side electronicdevice 5060. For example, the transmitting-side electronic device 5000may transmit the coordinate information for the current location of thetransmitting-side electronic device 5000 to the receiving-sideelectronic device 5060, as sharing data. As described above, the sharingdata transmitted from the transmitting-side electronic device 5000 maybe based on the first format by the data sharing platform according toan exemplary embodiment of the present disclosure. In this exemplaryembodiment, the first format may be coordinate information, and thetransmitting-side electronic device 5000 may transmit the coordinateinformation for the current location of the transmitting-side electronicdevice 5000, instead of the entirety of a map application executionscreen 5330, to the receiving-side electronic device 5060.

In operation 5055, the receiving-side electronic device 5060 may processand display the received sharing data. For example, as shown in FIG.54B, the receiving-side electronic device 5060 may process thecoordinates of the current location of the transmitting-side electronicdevice 5000, and display the current location 5326 of thetransmitting-side electronic device 5000 on the map. As described above,the map application executed by the receiving-side electronic device5060 may also be based on the first format, so the receiving-sideelectronic device 5060 may process the received coordinates of thecurrent location of the transmitting-side electronic device 5000. Thereceiving-side electronic device 5060 may display the current location5326 of the transmitting-side electronic device 5000 on the map, or mayoutput a variety of processing results.

Although the description has been made of a process in which afterrunning the sharing application, the receiving-side electronic device5060 processes and displays received sharing data, this is justillustrative. In another exemplary embodiment, the receiving-sideelectronic device 5060 may receive sharing data, determine the format ortype of the received sharing data, execute a sharing applicationcorresponding thereto to process the sharing data, and output theprocessing results.

FIGS. 55A and 55B illustrate application execution screens for a datasharing method according to various exemplary embodiments of the presentdisclosure.

FIG. 55A illustrates the map application execution screen 5310 displayedby the transmitting-side electronic device 5000. The transmitting-sideelectronic device 5000 may obtain sharing data based on a text input5510. The text input 5510 may be, for example, an address of a specificarea. As described above, the output data of the map applicationexecuted in the transmitting-side electronic device 5000 may becoordinate information (e.g., the first format). Accordingly, thetransmitting-side electronic device 5000 may transmit coordinateinformation corresponding to the address of the text input 5510 to thereceiving-side electronic device 5060, as sharing data.

FIG. 55B illustrates the map application execution screen 5320 displayedby the receiving-side electronic device 5060. The receiving-sideelectronic device 5060 may process the received coordinate informationand display the point 5520 corresponding to the address entered to thetransmitting-side electronic device 5000, on the map.

FIGS. 56A and 56B illustrate application execution screens for a datasharing method according to various exemplary embodiments of the presentdisclosure. In the example of FIGS. 56A and 56B, the transmitting-sideelectronic device 5000 and the receiving-side electronic device 5060 mayset an additional note 5610 that is entered on the electronic device, assharing data. The transmitting-side electronic device 5000 may transmitat least one of the input position and input time of the enteredadditional note 5610 to the receiving-side electronic device 5060, assharing data.

The receiving-side electronic device 5060 may process the receivedsharing data, and display the additional note 5620 on the map. Thereceiving-side electronic device 5060 may display the additional note5620 on the map application execution screen 5320 based on at least oneof the input position and input time of the additional note 5610. Theabove-described additional note may also be transmitted from thereceiving-side electronic device 5060 to the transmitting-sideelectronic device 5000. Accordingly, at least one of two-way editing,control and manipulation is possible.

FIGS. 57A and 57B illustrate application execution screens displayed onthe transmitting-side electronic device 5000 and the receiving-sideelectronic device 5060, respectively.

As shown in FIG. 57A, the transmitting-side electronic device 5000 maydisplay the phone application execution screen 5130. The user 1 of thetransmitting-side electronic device 5000 may enter a command to selectan address book-related sharing object 5139 as a sharing object. Thetransmitting-side electronic device 5000 may send a sharing request tothe receiving-side electronic device 5060.

The receiving-side electronic device 5060 may display a graphic userinterface 5750 for querying whether to share an address book-relatedsharing object, based on the received sharing request. The graphic userinterface 5750 for querying whether to accept sharing an addressbook-related sharing object may include a region 5751 corresponding to‘Accept’ and a region 5752 corresponding to ‘Reject’. The user of thereceiving-side electronic device 5060 may designate, for example, theregion 5751 corresponding to ‘Accept’, and the receiving-side electronicdevice 5060 may obtain a sharing acceptance in response to the entereddesignation.

As shown in FIG. 58A, the transmitting-side electronic device 5000 maydisplay a sharing application execution screen 5810 corresponding to thesharing object. The sharing application execution screen 5810 mayinclude information about at least one address book. Thetransmitting-side electronic device 5000 may obtain address bookinformation of, for example, “Linda”, as sharing data. Thetransmitting-side electronic device 5000 may transmit the obtainedsharing data (e.g., the address book information “Linda”) to thereceiving-side electronic device 5060. The sharing data may include atleast one of a name, a phone number and an e-mail address.

The receiving-side electronic device 5060 may receive the sharing data(e.g., the address book information “Linda”) from the transmitting-sideelectronic device 5000. Although the receiving-side electronic device5060 may display a sharing application execution screen corresponding tothe sharing object, the receiving-side electronic device 5060 may keepthe display of the phone application execution screen 5140 as shown inFIG. 58B.

As shown in FIG. 59A, after transmitting sharing data, thetransmitting-side electronic device 5000 may display again the phoneapplication execution screen 5130. As shown in FIG. 59B, thereceiving-side electronic device 5060 may run a sharing application anddisplay the sharing application execution screen. For example, thereceiving-side electronic device 5060 may run an address bookapplication and display an execution screen corresponding thereto. Thereceiving-side electronic device 5060 may process sharing data, anddisplay the processing results. For example, as shown in FIG. 59B, thereceiving-side electronic device 5060 may display an execution screen onwhich a name 5910 and a phone number 5911, which are included in thesharing data, are entered to the phone application. The phoneapplication may further include a save function key 5912. If the savefunction key 5912 is designated, the receiving-side electronic device5060 may store the sharing data. FIG. 60 illustrates a phone application6010 on which sharing data is stored by the receiving-side electronicdevice 5060. As shown in FIG. 60, the phone application 6010 may includea phone number 6011 of Linda.

FIG. 61 is a flowchart for a data sharing method of a transmitting-sideelectronic device according to various exemplary embodiments of thepresent disclosure.

In operation 6110, the transmitting-side electronic device may obtain asharing object.

In operation 6120, the transmitting-side electronic device may convertthe data corresponding to the sharing object into a first format. Morespecifically, the transmitting-side electronic device may run a sharingapplication corresponding to the sharing object. The data output fromthe sharing application may be data that is converted into the firstformat. The first format may be a format that is defined in common toboth of the transmitting-side electronic device and the receiving-sideelectronic device. For example, the sharing application may be producedbased on the data sharing platform. Accordingly, the transmitting-sideelectronic device may output the data that is converted into the firstformat.

In operation 6130, the transmitting-side electronic device may transmitthe converted data to the receiving-side electronic device.

FIG. 62 is a flowchart for a data sharing method of a receiving-sideelectronic device according to various exemplary embodiments of thepresent disclosure.

In operation 6210, the receiving-side electronic device may receive theconverted data.

In operation 6220, the receiving-side electronic device may run anapplication corresponding to the data. The receiving-side electronicdevice may determine a format of the converted data, and run anapplication corresponding to the determined format. In one exemplaryembodiment, the receiving-side electronic device may store arelationship between the data format and the application. Thereceiving-side electronic device may include a relationship between eachapplication and at least one data format required for each application.For example, the receiving-side electronic device may store arelationship indicating that a map application is related to a dataformat of coordinate information and a data format of a text.Accordingly, upon receiving sharing data of coordinate information, thereceiving-side electronic device may run a map application. As anotherexample, the receiving-side electronic device may store a relationshipindicating that a web browsing application is related to a data formatof a URL. Accordingly, upon receiving sharing data of URL, thereceiving-side electronic device may run a web browsing application.Accordingly, the receiving-side electronic device may run an applicationthat is different from the application that is executed in thetransmitting-side electronic device. For example, the receiving-sideelectronic device may store a relationship indicating that a weatherapplication is related to a data format of coordinate information. Thetransmitting-side electronic device may run a map application andtransmit the coordinate information to the receiving-side electronicdevice as sharing data. The receiving-side electronic device may run aweather application based on the received coordinate information, anddisplay the weather of the area.

Table 1 shows relationships between applications and their required dataformats according to various exemplary embodiments of the presentdisclosure.

TABLE 1 Application Data format Weather Application Weather information,coordinate information Map Application Coordinate information, textAddress Book Application Address book information

The above relationships may be defined in, for example, the data sharingplatform, and each application may be produced based on the data sharingplatform. Accordingly, although a map application produced by a companyA is different from a map application produced by a company B, the mapapplication produced by the company A and the map application producedby the company B can exchange and process coordinate information andtext information, since they are produced based on the same data sharingplatform.

In operation 6230, the receiving-side electronic device may process anddisplay the received sharing data.

FIG. 63 is a flowchart of a data sharing method according to variousexemplary embodiments of the present disclosure.

In operation 6310, a transmitting-side electronic device 6300 may obtaina sharing object.

In operation 6315, the transmitting-side electronic device 6300 may senda sharing request to a receiving-side electronic device 6360. Inoperation 6320, the receiving-side electronic device 6360 may obtain asharing acceptance response. In operation 6325, the receiving-sideelectronic device 6360 may send a sharing acceptance response to thetransmitting-side electronic device 6300.

In operation 6330, the transmitting-side electronic device 6300 may runa first application. In operation 6335, the receiving-side electronicdevice 6360 may run a second application. The second application may bedifferent from the first application.

In operation 6340, the transmitting-side electronic device 6300 mayobtain data of a first format, which is output from the firstapplication. In operation 6345, the transmitting-side electronic device6300 may transmit the data of the first format to the receiving-sideelectronic device 6360. In operation 6350, the receiving-side electronicdevice 6360 may display the received data based on the secondapplication.

In another exemplary embodiment, the receiving-side electronic device6360 may determine the format of the received data to run the secondapplication.

FIGS. 64A and 64B illustrate screens displayed by an electronic deviceaccording to various exemplary embodiments of the present disclosure. Anexample of FIGS. 64A and 64B will be described in more detail withreference to FIG. 64C. FIG. 64C is a flowchart of a data sharing methodaccording to an exemplary embodiment of the present disclosure.

Referring to FIG. 64C, in operation 6420, a transmitting-side electronicdevice 6400 may run a map application. For example, as shown in FIG.64A, the transmitting-side electronic device 6400 may display a mapapplication execution screen 5310.

In operation 6425, the transmitting-side electronic device 6400 mayobtain location information. For example, as shown in FIG. 64A, thetransmitting-side electronic device 6400 may obtain location information5316 corresponding to one point on the map application execution screen5310.

In operation 6430, the transmitting-side electronic device 6400 mayconvert the location information into coordinate information (e.g., thefirst format), and output the coordinate information. The mapapplication of the transmitting-side electronic device 6400 may beproduced to output coordinate information during its production. In thiscase, the transmitting-side electronic device 6400 may not performseparate data conversion.

In operation 6435, the transmitting-side electronic device 6400 maytransmit the coordinate information of the first format to thereceiving-side electronic device 6460.

In operation 6440, the receiving-side electronic device 6460 maydetermine the first format of the data. In other words, thereceiving-side electronic device 6460 may determine that the receiveddata is coordinate information.

In operation 6445, the receiving-side electronic device 6460 may run aweather application on the received data. For example, as shown in FIG.64B, the receiving-side electronic device 6460 may display a weatherapplication execution screen 6410.

In operation 6450, the receiving-side electronic device 6460 may processthe coordinate information and display the weather corresponding to thelocation information. The receiving-side electronic device 6460 maydetermine that the area corresponding to the coordinate information is‘Suwon’, and obtain and display the weather information for the Suwonarea. The receiving-side electronic device 6460 may get the weatherinformation for the Suwon area by querying the outside about the weatherinformation.

FIGS. 65A and 65B illustrate screens displayed by an electronic deviceaccording to various exemplary embodiments of the present disclosure.

FIG. 65A illustrates a web browsing application execution screen 6510that is executed in a transmitting-side electronic device. The webbrowsing application execution screen 6510 may include a name 6512 and aphone number 6515. The transmitting-side electronic device may transmitthe name and phone number to the receiving-side electronic device in theformat of user information.

FIG. 65B illustrates an address book application execution screen 6520that is executed in a receiving-side electronic device. Thereceiving-side electronic device may determine the format of thereceived user information, and run an address book application. Thereceiving-side electronic device may display the address bookapplication execution screen 6520, and may enter and display a name 6521and a phone number 6522, which are the received sharing data. Theaddress book application execution screen 6520 may further include asave function key 6523. If the save function key 6523 is clicked, thereceiving-side electronic device may save the received sharing data.

FIG. 66 is a conceptual diagram illustrating a system hierarchyaccording to various exemplary embodiments of the present disclosure.

As shown in FIG. 66, an application layer 6620 may be defined on the topof the system area 6610. In the application layer 6620 may be defined afirst application 6621, a second application 6622 and a mediation agent6623. The mediation agent 6623 may process data from the firstapplication 6621 in a first format (in operation 6630), and output tothe processing results to the second application 6622 (in operation6640). Both of the first application 6621 and the second application6622 may be produced based on the mediation agent 6623.

FIGS. 67A to 67D are flowcharts of a data sharing method according tovarious exemplary embodiments of the present disclosure.

In operation 6721, a transmitting-side electronic device 6700 may run aphone application.

In operation 6723, the transmitting-side electronic device 6700 may senda service subscription and authentication request to a subscriber server6713. In operation 6725, the subscriber server 6713 may send asubscription confirmation response (authentication) to thetransmitting-side electronic device 6700.

In operation 6727, the transmitting-side electronic device 6700 mayperform dialing with a called number. The transmitting-side electronicdevice 6700 may receive a called number and a dialing command through aphone application, and perform dialing with the obtained called number.

In operation 6729, the transmitting-side electronic device 6700 may senda voice call connection request to an IMS network 6710. In operation6731, the IMS network 6710 may forward the called number provided fromthe transmitting-side electronic device 6700, to the subscriber server6713. In operation 6733, the subscriber server 6713 may send a queryrequest for callee information and receiving-side Value-Added Service(VAS) server information to a relay server 6715. In operation 6735, therelay server 6715 may transmit the query information (e.g., at least oneof the callee information and receiving-side VAS server information) tothe IMS network 6710. In operation 6737, the IMS network 6710 maytransmit the received query information to the transmitting-sideelectronic device 6700. In operation 6739, the transmitting-sideelectronic device 6700 may send a data session connection request to therelay server 6715 based on the received query information. Thetransmitting-side electronic device 6700 may send the data sessionconnection request based on the information related to the voice call.The transmitting-side electronic device 6700 may send the data sessionconnection request based on TCP or BIND. In operation 6741, thetransmitting-side electronic device 6700 and the relay server 6715 maygenerate a transmitting-side (UE-1) session.

In operation 6743, the IMS network 6710 may send a voice call connectionrequest to a receiving-side electronic device 6760. In operation 6745,the receiving-side electronic device 6760 may run a phone application.In operation 6747, the receiving-side electronic device 6760 may send aservice subscription and authentication request to the subscriber server6713. In operation 6749, the subscriber server 6713 may send asubscription confirmation response (authentication) to thereceiving-side electronic device 6760.

In operation 6751, the relay server 6715 may transmit recipient profileinformation (e.g., screen configuration information) to thetransmitting-side electronic device 6700. In operation 6753, thetransmitting-side electronic device 6700 may configure and display anOutgoing Call screen.

In operation 6755, the IMS network 6710 may transmit a caller number tothe subscriber server 6713. In operation 6757, the subscriber server6713 may send a query request for caller information andtransmitting-side VAS server information to the relay server 6715. Inoperation 6759, the relay server 6715 may transmit the query informationto the IMS network 6710. In operation 6761, the IMS network 6710 maytransmit the received information to the receiving-side electronicdevice 6760. In operation 6763, the receiving-side electronic device6760 may send a data session connection request to the relay server6715. The receiving-side electronic device 6760 may send the datasession connection request based on TCP or BIND. In operation 6765, thereceiving-side electronic device 6760 and the relay server 6715 maygenerate a receiving-side (UE-2) session. In operation 6767, thetransmitting-side electronic device 6700 and the receiving-sideelectronic device 6760 may connect a data session.

In operation 6769, the relay server 6715 may transmit caller profileinformation to the receiving-side electronic device 6760. In operation6771, the receiving-side electronic device 6760 may configure anddisplay an Incoming Call screen. In operation 6773, the receiving-sideelectronic device 6760 may respond to the voice call connection. Inoperation 6775, the transmitting-side electronic device 6700 and thereceiving-side electronic device 6760 may connect a voice call.

In operation 6779, the transmitting-side electronic device 6700 maydisplay a sharing object. In operation 6781, the transmitting-sideelectronic device 6700 may detect a selection of the sharing object. Inoperation 6783, the transmitting-side electronic device 6700 may send asharing request for the sharing object to the relay server 6715. Inoperation 6785, the relay server 6715 may send a sharing request for thesharing object to the receiving-side electronic device 6760. Inoperation 6787, the receiving-side electronic device 6760 may detect aselection of a Sharing Accept icon, so the receiving-side electronicdevice 6760 may obtain a sharing acceptance. In operation 6789, thereceiving-side electronic device 6760 may send a sharing acceptance tothe relay server 6715. In operation 6791, the receiving-side electronicdevice 6760 may run a sharing application corresponding to the requestedsharing object. In operation 6793, the relay server 6715 may send thesharing acceptance to the transmitting-side electronic device 6700. Inoperation 6795, the transmitting-side electronic device 6700 may run asharing application. In operation 6797, the transmitting-side electronicdevice 6700 may obtain sharing data. In operation 6799, thetransmitting-side electronic device 6700 may transmit the sharing datato the relay server 6715. In operation 6801, the relay server 6715 maytransmit the sharing data to the receiving-side electronic device 6760in a relay manner. In operation 6803, the receiving-side electronicdevice 6760 may process and output the sharing data, completing the datasharing.

FIG. 68 is a block diagram of a heterogeneous application processingagent in view of modules according to various exemplary embodiments ofthe present disclosure.

A heterogeneous application processing agent 6800 may include at leastone of a location information object processing module 6810, a contactobject processing module 6820, a traffic situation object processingmodule 6830, a public transport object processing module 6840, a URLobject processing module 6850, and a profile object processing module6860.

The location information object processing module 6810 may convert thedata from an application which processes location information-relateddata into a format used in the data sharing platform. The contact objectprocessing module 6820 may convert the data from an application whichprocesses contact-related data into a format used in the data sharingplatform. The traffic situation object processing module 6830 mayconvert the data from an application which processes trafficsituation-related data into a format used in the data sharing platform.The public transport object processing module 6840 may convert the datafrom an application which processes public transport-related data into aformat used in the data sharing platform. The URL object processingmodule 6850 may convert the data from an application which processesURL-related data into a format used in the data sharing platform. Theprofile object processing module 6860 may convert the data from anapplication which processes profile-related data into a format used inthe data sharing platform.

Table 2 below shows a table for a heterogeneous application processingagent in view of a table.

TABLE 2 Module types Type Type format User profile JSON Object { ‘name’:‘user_name’, ‘number’: ‘number’, ‘birthday’: ‘birthday’, ‘gender’:[‘male’, ‘female’], ... job / age / height / weight / etc. } URL StringURL Public transport info JSON Object { ‘region’: [‘Seoul’, ‘Inchon’,‘Daejeon’,, ...], ‘number’: [‘0’, ‘1’, ‘2’, ...], ‘interval’: [‘10’,‘12’, ‘15’, ...], ... }

Only a few modules are disclosed in Table 2, but it will be apparent tothose of ordinary skill in the art that the type and type format forlocation information, contact, traffic situation and the like may alsobe additionally defined.

The term ‘module’ or ‘unit’ as used herein may refer to a unit thatincludes any one or a combination of, for example, hardware, softwareand firmware. The ‘module’ may be interchangeably used with a term suchas, for example, unit, logic, logical block, component, or circuit. The‘module’ may be the minimum unit of an integrally configured part, or apart thereof. The ‘module’ may be the minimum unit for performing one ormore functions, or a part thereof. The ‘module’ may be implementedmechanically or electronically. For example, the ‘module’ according tovarious exemplary embodiments of the present disclosure may include atleast one of an Application-Specific Integrated Circuit (ASIC) chip,Field-Programmable Gate Arrays (FPGAs), or a programmable-logic device,which are known or will be developed in the future, and which performcertain operations.

In various exemplary embodiments, at least a part of the apparatus(e.g., modules or functions thereof) or method (e.g., operations)according to various exemplary embodiments of the present disclosure maybe implemented, for example, by an instruction(s) that is stored incomputer-readable storage media in the form of a programming module. Ifthe instruction is executed by one or more processors (e.g., theprocessor 120), the one or more processors may perform the functioncorresponding to the instruction. The computer-readable storage mediamay be, for example, the memory 130. At least a part of the programmingmodule may be implemented (e.g., executed) by, for example, theprocessor 120. At least a part of the programming module may include,for example, a module, a program, a routine, a set of instructions, or aprocess, for performing one or more functions.

A computer-readable recording medium may include magnetic media (e.g.,hard disks, floppy disks, and magnetic tape), optical media (e.g.,Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD)),magneto-optical media (e.g., floptical disk), and hardware devices(e.g., Read Only Memory (ROM), Random Access Memory (RAM) and flashmemory) specially configured to store and perform program instructions(e.g., programming modules). The program instructions may include notonly the machine code produced by a compiler, but also the high-levellanguage code that can be executed by a computer using an interpreter orthe like. The above hardware device may be configured to operate as oneor more software modules to perform operations according to variousexemplary embodiments of the present disclosure, and vice versa.

The module or programming module according to various exemplaryembodiments of the present disclosure may include at least one of theabove-described components, or some of them may be omitted.Alternatively, the module or programming module may further includeother additional components. Operations performed by the module,programming module or other components according to various exemplaryembodiments of the present disclosure may be executed in a sequential,parallel, iterative, or heuristic manner. Some operations may beexecuted in a different order, or may be omitted. Alternatively, otheroperations may be added.

In accordance with various exemplary embodiments of the presentdisclosure, in a storage medium storing instructions, the instructionsare set to allow at least one processor to perform at least oneoperation when the instructions are executed by the at least oneprocessor. The at least one operation may include an operation ofconnecting a voice call with a receiving-side electronic device; anoperation of obtaining a sharing object to be shared with thereceiving-side electronic device; and an operation of transmitting datacorresponding to the sharing object to the receiving-side electronicdevice through a data session formed based on the information related tothe voice call.

As is apparent from the foregoing description, according to an exemplaryembodiment of the present disclosure, a transmitting-side electronicdevice may share data corresponding to a sharing object with areceiving-side electronic device during the voice call connection.

According to an exemplary embodiment of the present disclosure, thetransmitting-side electronic device may display the sharing object forsharing data on a Phone Conversation screen.

According to an exemplary embodiment of the present disclosure, thetransmitting-side electronic device may share the data during the voicecall connection, without the need to perform a separate connectionprocess or run an application.

According to an exemplary embodiment of the present disclosure, thetransmitting-side electronic device may share data with thereceiving-side electronic device even with the transmission of lessdata, compared with the high-data traffic scheme such as video calls.

According to an exemplary embodiment of the present disclosure, thetransmitting-side electronic device and the receiving-side electronicdevice may share a control command.

While the disclosure has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method performed by a transmitting-sideelectronic device for sharing data with a receiving-side electronicdevice, the method comprising: connecting a call with the receiving-sideelectronic device using a call application; receiving a sharing requestfor first content made at the receiving-side electronic device;receiving a first user input for accepting the sharing request; inresponse to the first user input for accepting the sharing request,receiving information associated with the first content while executingthe call; displaying the first content on a screen of the callapplication, based on the information of the first content; receiving asecond user input on the first content; in response to the second userinput on the first content, transmitting information associated with thesecond user input to the receiving-side electronic device through a datasession formed based on information related to the call after the callis connected; and displaying first updated content generated based onthe second user input on the first content.
 2. The method of claim 1,wherein the connecting the call with the receiving-side electronicdevice comprises: displaying an execution screen of the callapplication; transmitting a request for connecting the call with thereceiving-side electronic device via the call application; and inresponse to receiving a connection acceptance from the receiving-sideelectronic device, connecting the call with the receiving-sideelectronic device.
 3. The method of claim 2, wherein the transmittingthe request for connecting the call comprises: transmitting a callednumber via the call application; receiving a content of a receiving-sideoperator corresponding to the called number; and displaying the receivedcontent of the receiving-side operator on a call send standby screen ofthe call application.
 4. The method of claim 3, wherein the content ofthe receiving-side operator includes an advertising image of thereceiving-side operator, or an item or menu provided by an automaticresponse system (ARS).
 5. The method of claim 3, further comprising:receiving at least one of callee information and receiving-sideValue-Added Service (VAS) server information corresponding to the calledinformation; and generating the data session based on the at least oneof the received callee information and the receiving-side VAS serverinformation.
 6. The method of claim 1, further comprising: in responseto receiving a call termination request, terminating the call with thereceiving-side electronic device; receiving confirmed service data; anddisplaying the confirmed service data on the screen of the callapplication.
 7. The method of claim 1, further comprising: in responseto a third user input on the first content at the receiving-sideelectronic device, receiving a second updated content which is generatedbased on the third user input; and displaying the second updated contenton the screen of the call application.
 8. The method of claim 7, whereinthe receiving-side electronic device displays the second updated contentin response to identifying the third user input on the first content. 9.The method of claim 1, further comprising: in response to executing thecall application, transmitting a service subscription and authenticationrequest to a subscriber server; and receiving at least one of asubscription confirmation response or authentication response before thecall is connected to the receiving-side electronic device.
 10. Atransmitting-side electronic device communicating with a receiving-sideelectronic device, the transmitting-side electronic device comprising: adisplay; a communication interface; and a processor configured to:connect a call with the receiving-side electronic device using the callapplication, receive a sharing request for first content made at thereceiving-side electronic device through the communication interface,receive a first user input for accepting the sharing request, inresponse to the first user input for accepting the sharing request,receive information associated with the first content while executingthe call, display the first content on the screen of the callapplication, based on the information of the first content, receive asecond user input on the first content, in response to the second userinput on the first content, transmit information associated with thesecond user input to the receiving-side electronic device through a datasession formed based on information related to the call after the callis connected, and display first updated content generated based on thesecond user input on the first content.
 11. The transmitting-sideelectronic device of claim 10, wherein the processor further configuredto: display an execution screen of the call application, transmit arequest for connecting the call with the receiving-side electronicdevice via the call application, and in response to receiving aconnection acceptance from the receiving-side electronic device,connecting the call with the receiving-side electronic device.
 12. Thetransmitting-side electronic device of claim 11, wherein the processorfurther configured to: transmit a called number via the callapplication, receive a content of a receiving-side operatorcorresponding to the called number; and displaying the received contentof the receiving-side operator on a call send standby screen of the callapplication.
 13. The transmitting-side electronic device of claim 12,wherein the content of the receiving-side operator includes anadvertising image of the receiving-side operator, or an item or menuprovided by an automatic response system (ARS).
 14. Thetransmitting-side electronic device of claim 12, wherein the processorfurther configured to: receive at least one of callee information andreceiving-side Value-Added Service (VAS) server informationcorresponding to the called information, and generate the data sessionbased on the at least one of the received callee information and thereceiving-side VAS server information.
 15. The transmitting-sideelectronic device of claim 10, wherein the processor further configuredto: in response to receiving a call termination request, terminate thecall with the receiving-side electronic device, receive confirmedservice data, and display the confirmed service data on the screen ofthe call application.
 16. The transmitting-side electronic device ofclaim 10, wherein the processor further configured to: in response to athird user input on the first content at the receiving-side electronicdevice, receive a second updated content which is generated based on thethird user input, and display the second updated content on the screenof the call application.
 17. The transmitting-side electronic device ofclaim 16, wherein the receiving-side electronic device displays thesecond updated content in response to identifying the third user input.18. The transmitting-side electronic device of claim 10, wherein theprocessor further configured to: in response to executing the callapplication, transmit a service subscription and authentication requestto a subscriber server, and receive at least one of a subscriptionconfirmation response or authentication response before the call isconnected to the receiving-side electronic device.